run_command

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses the critical behavioral trait that it can run arbitrary commands and provides a caution. No annotations exist, so the description carries the full transparency burden and does so effectively. Lacks specifics about exit codes, timeout, or working directory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, minimal waste, front-loaded with purpose, followed by important technical detail and a caution. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (which handles return values) and simple schema, the description is mostly complete. However, a command execution tool would benefit from mentioning things like timeout behavior, environment variables, or potential side effects on the system.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with a clear parameter description. The description adds value by explaining the execution environment (cmd or sh) and supported features (pipes, redirects, chaining).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly defines the tool as executing a shell command and returning output. Distinct from siblings like 'python_code', 'grep', 'delete_folder', etc., which have narrower scopes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly notes the command runs through the platform shell and that pipes/redirects/chained commands work. Includes a caution about arbitrary commands. Could further clarify when to use this versus Python-specific tools like 'python_code'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.