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

While annotations confirm it's read-only, the description adds valuable context by specifying that explanations are sourced 'from man pages.' This informs the agent about the authoritative source of the knowledge and confirms it is a documentation tool rather than an execution environment.

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 extremely concise and efficiently communicates its core functionality in a single, well-structured sentence.

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?

The definition is adequate for a simple utility, but because it lacks structured parameter details (0% coverage), the description should ideally explain the expected complexity of the input command (e.g., handling quotes or pipes) for complete usability.

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 0%, yet the description only advises the user to 'Paste a command.' It fails to provide guidance on command complexity, expected format, or potential edge cases, leaving the description unable to compensate for the lack of structured data.

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 that the tool provides explanations for shell commands, including flags, pipes, and redirections. It is distinct from infrastructure/cell-related tools in the provided sibling list because its function is explanatory, not operational.

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?

Usage is implied: use this when a user needs an explanation of shell syntax or specific commands. However, it does not explicitly guide when to use it versus when to use general coding help or other shell utility tools.

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