shell_execute

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

With no annotations provided, the description carries the burden and delivers useful behavioral details: the default (30s) and maximum (300s) timeout, and the output cap (1048576 bytes). It also implicitly indicates read-only operations via the allowed command list, though it does not disclose exit-code handling or output format.

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 compact and front-loaded with the primary purpose, but the line 'Allowed patterns:' is empty and incomplete, which is wasted space and a structural gap. Overall it is fairly concise, but the unresolved placeholder keeps it from being a 4 or 5.

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 lack of an output schema and annotations, the description should explain what the tool returns (e.g., stdout, stderr, exit code) but does not. It covers the main execution constraints (allowed commands, timeout, output cap), but return value and error behavior are missing, making it only partially complete.

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 covers all parameters (100%), so baseline is 3. The description adds value beyond the schema by specifying the allowed commands for the command parameter and the default/max timeout values, which are not in the schema. This extra context justifies a 4.

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 and enumerates the allowed commands (cat, grep, ls, pwd, wc), giving a specific verb, resource, and scope. This distinguishes it from general shell executors and is unambiguous even without sibling 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?

The allowed commands list provides clear context about when this tool is appropriate, effectively excluding all other commands. However, it does not mention any alternative tool or explicitly state when not to use it, so it falls short of a 5.

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