execute_command

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

With no annotations, the description must disclose the tool's behavioral traits. It provides some context (local shell vs. proot sandbox, Node/wrangler installed) but fails to mention critical safety aspects such as potential destructive effects, permission model, output behavior, or timeout handling. This is a significant gap for an arbitrary command 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 a single concise sentence that is front-loaded with the key verb. However, it is too underspecified for a tool of this complexity; an effective description would include safety and output notes, making the current version too short to be fully useful.

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 no annotations, no output schema, and a complex tool that executes arbitrary commands, the description lacks essential information about return values (stdout/stderr), error handling, and execution environment details beyond the backend distinction. This incomplete context would leave an agent uncertain about how to interpret results or handle failures.

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?

The input schema already describes all three parameters (command, cwd, timeout) with clear descriptions, so schema coverage is 100%. The tool description only repeats the cwd default, adding no new parameter-level insight beyond what the schema provides, thus baseline score of 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?

The description clearly states it executes arbitrary shell commands in the workspace, using the verb 'execute' and resource 'shell commands'. This distinguishes it from sibling tools like read_file, write_file, and cloudflare_api, which handle file operations and API calls respectively.

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 usage (if you need to run a shell command) but does not explicitly mention when to use this tool over alternatives, nor does it state exclusions. It mentions backend differences (local vs. proot) but these are about behavior, not usage guidance.

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