Execute Shell Command

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

The annotations already indicate destructiveHint=true and readOnlyHint=false, which the description aligns with by describing command execution. The description adds valuable behavioral context beyond annotations: safety warnings about unsafe commands, constraints on process types, and output format details. However, it doesn't mention rate limits, authentication needs, or specific error handling behaviors.

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 appropriately sized and front-loaded with the core purpose. The safety warnings and usage constraints are efficiently presented. However, the formatting with asterisks and some redundancy ('Returns a JSON object...' could be integrated more smoothly) prevents a perfect score.

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 high-risk nature of shell command execution, the description provides excellent contextual completeness. It covers safety constraints, usage boundaries, output format, and references to memory checks. With annotations covering destructive/read-only aspects and an output schema presumably detailing the JSON response, no significant gaps remain.

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?

With 100% schema description coverage, the input schema already documents all 4 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline score of 3 reflects adequate coverage through structured data alone.

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 specific action ('Execute a shell command and return its output') and distinguishes it from all sibling tools, which are focused on file operations, memory management, and project configuration rather than shell command execution. The verb+resource combination is precise and unambiguous.

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 explicit guidance on when NOT to use this tool ('Never execute unsafe shell commands!', 'Do not use this tool to start long-running processes...', 'processes that require user interaction') and references an alternative approach ('If there is a memory about suggested commands, read that first'). This gives clear boundaries for appropriate usage.

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