bash

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

The description adds the return format (exit code, stdout, stderr) which is not in the annotations. However, it does not elaborate on side effects or the fact that arbitrary commands can be destructive, though the destructiveHint annotation already signals this.

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, front-loaded sentence with no wasted words. It immediately states the action and expected outputs.

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 complete schema with full parameter descriptions, an existing output schema, and the destructiveHint annotation, the description is sufficient for a basic understanding. It could add usage warnings, but the structured fields cover the main safety concern.

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 description coverage is 100% for all three parameters (cwd, command, timeout), so the description does not need to repeat parameter details. The description itself adds no parameter-level semantics, but the schema already provides them.

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 uses a specific verb 'Execute' with a clear resource 'a shell command' and explicitly states the return values (exit code, stdout, stderr). This clearly distinguishes it from siblings like read, grep, find, ls, write, and edit which are file-specific.

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 provides no guidance on when to use bash versus dedicated tools like read, grep, or find. It does not mention exclusions or alternatives, leaving the agent to infer usage from the tool name.

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