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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether commands execute immediately, whether they are destructive, what permissions or sandboxing apply, or what is returned. For an arbitrary command execution tool this is the most important missing information.

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?

It is very short, but brevity here reflects under-specification rather than economy. The one clause present adds no information an agent could act on.

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?

A command-execution tool with no annotations, no output schema, no permission/risk disclosure, and no sibling differentiation is far too thin for an agent to invoke safely or correctly. Everything an agent needs is missing.

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 the single 'detail' parameter, so the baseline is 3. The description adds no meaning beyond the schema, but the schema itself is thin ('Specific parameters for this action'), so no credit above baseline.

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 restates the tool name ('sh') and adds only the vague qualifier 'Terminal command (runner operator)', which is effectively a tautology. It does not distinguish this tool from siblings bash, zsh, or converse, nor does it say what a terminal command runner actually does (execute shell commands, spawn a shell session, etc.).

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?

There is no guidance on when to use sh versus the sibling tools bash or zsh, nor when-not to use it. Given that three near-identical shell tools exist, the absence of any routing guidance is a serious gap.

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