execute_shell

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

No annotations exist, so description must fully disclose behavior. It mentions OS-specific shells but omits side effects, output format, synchronous vs async execution, privilege requirements, and error handling. Minimal transparency for a shell execution tool.

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?

The description is brief (two sentences plus example) and front-loaded. However, it could be more structured (e.g., separate parameter descriptions). 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 an output schema existing (reducing need for return value explanation), the description lacks usage guidelines, behavioral transparency, and complete parameter semantics. It is not comprehensive for a shell execution tool.

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 0%, so description must explain parameters. It describes 'command' with examples but completely omits 'agent_id', a required parameter. Adding meaning only for one of two parameters is insufficient.

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?

The description clearly states the tool executes a shell command via cmd.exe or /bin/sh, providing specific verb and resource. Examples like 'whoami /all' reinforce purpose. It distinguishes from siblings like execute_powershell and execute_raw.

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?

The description implies use for shell commands but does not explicitly state when to use this tool versus alternatives like execute_powershell or run_process. No when-not-to-use guidance or exclusions are provided.

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