shell_execute

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

With no annotations, the description carries full burden. It discloses timeout limits and output cap, but does not address potential side effects, safety, or authentication requirements. The allowed commands imply safety, but the description could be more explicit about the behavioral impact of executing 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?

The description is concise (5 lines), front-loads the action, and uses list format for constraints. Every sentence is informative with no redundancy.

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 output schema, the description explains key constraints (allowed commands, timeouts, output cap). It does not describe return value format or error handling, which would improve completeness, but it covers the most critical aspects 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 100%, baseline is 3. The description adds value by specifying default timeout (30s), maximum timeout (300s), and output cap (1048576 bytes), which are not in the schema. It also reinforces which commands are allowed, aiding parameter understanding.

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 'Execute a shell command' and lists allowed commands (ls, pwd, grep, wc, cat), making the purpose and scope unambiguous.

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 explicitly lists allowed commands and patterns, providing clear usage restrictions. It also mentions default and maximum timeout and output cap, helping agents decide if the tool fits their needs. However, it does not provide explicit when-not-to-use guidance or sibling comparisons.

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