bash

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

With no annotations, the description carries the burden of behavioral disclosure. It does reveal that 'Output is capped; complete truncated output is saved to a file,' which is useful. But it does not mention exit codes, error handling, or potential side effects of running arbitrary commands, leaving some gaps.

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 three concise sentences, each earning its place: purpose, usage guidance, and a behavioral note. No wasted words or repetition of schema details.

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?

For a simple tool with no output schema and straightforward parameters, the description covers key points: execution, timeout units, and output handling. However, it omits details about command compatibility (e.g., shell used) or error behavior, which could be relevant but are not strictly required given the simple schema.

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 schema description coverage is 100% since all parameters have descriptions. The tool description adds a bit of value by reinforcing the unit for timeout and advising against 'cd' commands, but these are largely redundant with schema text. The additional guidance on workdir is helpful but not enough to exceed the baseline of 3.

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' with a specific verb and resource. It is unambiguous and distinguishes this tool from siblings like file operations or web searches which have different purposes.

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 gives clear practical guidance: 'Set workdir instead of changing directories inside the command when possible' and specifies that timeout is in milliseconds. However, it does not explicitly discuss when to prefer bash over sibling tools or exclude scenarios, though the context implies bash is for running shell commands.

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