execute_shell

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

Discloses key behavioral traits: sandboxed execution, isolation in Seatbelt sandbox, and blocking of dangerous patterns (rm -rf, sudo, curl, wget). No annotations provided, so description carries full burden; describes restrictions but not error behavior on blocked commands.

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?

Two concise sentences with no redundant information. Front-loaded with purpose and key restrictions.

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 (covering return values) and only 2 parameters, the description adequately covers purpose, restrictions, and relative usage. No significant gaps identified.

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 coverage is 100% with both parameters described in schema. Description adds no additional parameter details beyond what schema already provides, so baseline 3 is appropriate.

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 the tool executes a shell command in a sandboxed environment, with a specific verb and resource. Distinguishes from sibling tool 'execute_code' by noting it is more restrictive than Python execution.

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?

Provides comparative context with Python execution, indicating when shell might be less appropriate, but lacks explicit when-not or alternative tool recommendations for other scenarios.

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