run_shell_command

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

With no annotations, the description only states it returns stdout/stderr and mentions working_dir default. Omitted behavioral traits like timeouts, error handling, security implications, or that it blocks execution.

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: purpose, usage examples, parameter explanation. Front-loaded and concise with no unnecessary words.

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?

Despite having an output schema, the description lacks critical details for a shell command tool such as environment, permissions, and safety considerations. Incomplete for a potentially dangerous operation.

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 description coverage is 0%, but description explains both parameters: command is the shell command, working_dir is optional absolute path defaulting to home directory. Adds meaningful context beyond schema.

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 states it executes a shell command and returns stdout/stderr. Provides specific use cases like creating directories, installing packages, running scripts, which distinguishes it from file reading/writing tools.

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?

Does not mention when to avoid this tool or compare to sibling tools like run_background_process. Provides no guidance on choosing between synchronous vs background execution.

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