bash

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

No annotations provided; description only mentions streaming output. Does not disclose potential destructive actions (e.g., rm, dd) or other safety behaviors. Fails to provide adequate transparency for a command execution tool.

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?

Concise single sentence plus a list of common scenarios; no wasted words. Structured effectively for quick understanding.

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?

No output schema; description mentions streaming output but lacks details on exit codes, stderr handling, or security considerations. Minimum viable but could be more complete for a potentially dangerous 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 covers all 3 parameters with descriptions (100% coverage). Description adds no parameter-specific details beyond schema, so baseline score of 3 is appropriate.

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?

Description clearly states it executes commands in a local shell, supports streaming output, and lists common use cases (file operations, system info, CLI tools), distinguishing it from siblings node and python.

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?

Implicitly suggests use for shell commands via listed scenarios, but lacks explicit guidance on when to choose this tool over siblings (node, python). No alternatives or when-not-to-use mentioned.

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