inspect

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

Discloses the side effect of writing a debug report to output_dir/inspect.md. No annotations exist, so description carries full burden; additional details on read-only nature could improve score.

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?

Two concise paragraphs with clear structure: first explains what the tool does, second gives usage guidance and parameter hint. No wasted words.

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?

For a single-parameter tool with an output schema, the description fully covers input purpose, output side effect, and usage scenario. No 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?

The description adds meaning to the 'ref' parameter beyond the schema by providing an example format 'run_id/agent_id'. With 0% schema coverage, this compensation is effective but still basic.

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 inspects an agent's full execution state, listing specific components (partial output, stream log, files produced). This distinguishes it from sibling tools that execute or manage agents.

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?

Explicitly says 'Use after a timeout, crash, or unexpected result to understand what happened', providing clear context for when to use this tool vs alternatives.

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