Generate report

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

Annotations already indicate idempotent (idempotentHint=true) and non-destructive (destructiveHint=false), so the description has lower burden. However, it adds no extra behavioral context (e.g., whether this is a safe read, if it caches results, or what the output format entails). The description does not contradict annotations.

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 a single 10‑word sentence that efficiently conveys the core purpose. Every word earns its place, with no fluff or redundancy.

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 exists, and the description fails to mention the return type (e.g., string) or content of the report. Given the tool's moderate complexity (2 parameters, no nested objects), a complete description should clarify the output nature and any relevant side effects.

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 0%, so the description must compensate. It hints at the 'format' parameter through 'Markdown and/or JSON' but does not explicitly describe 'captureId' beyond the implied 'for a capture'. This adds partial value but leaves the required parameter underspecified.

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 generates a diagnostic report for a capture, specifying both Markdown and JSON formats. This verb-resource combination distinguishes it from sibling tools like webgl_get_capture_overview or webgl_run_diagnostics, which serve different purposes.

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?

No guidance on when to use this tool versus alternatives (e.g., webgl_get_capture_overview, webgl_run_diagnostics). The description lacks context on prerequisites, such as requiring a capture to exist first, or any exclusion criteria.

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