timeout

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

The annotation declares readOnlyHint=true, but the description describes a command execution tool that can have side effects (running arbitrary commands), which is a serious contradiction. No further behavioral context is added beyond the direct contradiction.

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 four sentences, all substantive, with no wasted words. Front-loaded with primary action, then behavior, then usage guidance.

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 description covers purpose, behavior, usage guidelines, and return format (JSON with output and timeout flag). Lacks mention of error handling or side effects but is sufficient for a tool with no output schema and good annotations aside from the contradiction.

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 100% with good parameter descriptions. The description doesn't add significant meaning beyond the schema, but it reinforces the behavior of max_output_bytes. Baseline 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?

The description clearly states the tool runs a command with a bounded time limit, automatically terminating it if exceeded, and captures output. It distinguishes itself from siblings like 'sleep' and 'nice' via explicit exclusion statements.

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 explicitly states when to use the tool ('prevent runaway commands') and when not to, providing specific alternatives ('use sleep to pause', 'use nice for CPU priority'), and references sibling tools.

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