Principle

Prefer a task-shaped tool to an open-ended one

A function named `create_invoice_draft` has fewer dangerous interpretations than `run_anything`.

About 1 min read

Before you use it

Use when
  • An agent can accomplish a job either through a narrow function or through a general shell, browser or arbitrary-request tool.

Keep this limit in mind

  • Over-fragmented tools can make workflows brittle; use the narrowest interface that still represents the real job.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

When practical, expose a function whose inputs and effects match the intended action instead of an open-ended executor. Narrow tools make authorization, validation, logging and testing more specific. General tools remain useful for expert work, but they deserve stronger containment because their action space is much larger.

An example

Use a repository file-update function for a known path rather than giving a content agent an unrestricted shell.

Check your result

The chosen tool exposes no broad capability merely because it was easier to integrate.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingPrefer a task-shaped tool to an open-ended one

Evidence and sources
Supports

OWASP recommends avoiding open-ended agent extensions where more granular task-specific functionality can be used.

General tools may be justified for expert workflows, but they require stronger containment and authorization.

LLM06:2025 Excessive Agency · Avoid open-ended extensions

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details