Get BugSnap bug report, annotated screenshot & fix guidance

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

No annotations exist, so the description carries the full burden. It discloses the shape of the return payload in detail (eight content categories), which is genuinely useful, but says nothing about access requirements, whether the capture must exist, error behavior on a bad UUID, or payload size — gaps that matter for an unannotated tool.

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?

One long sentence, but front-loaded with the purpose and organized as a numbered inventory, so it scans cleanly. The enumeration is lengthy yet justified because there is no output schema to describe the response.

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-item read tool with no output schema and no annotations, the description covers the return payload thoroughly and states the input format. It stops short of error/empty-state behavior or any note about the volume of data returned, which would complete the picture.

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% and the single parameter already documents both accepted forms. The description's closing line about accepting 'a bare capture UUID or a full BugSnap share URL' restates the schema rather than adding format, validation, or failure semantics, so baseline 3 applies.

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?

States a specific verb and resource ('Get complete, multimodal debugging context for a BugSnap bug report') and enumerates exactly what that context contains. It does not explicitly name the sibling bugsnap_list_captures, but the singular capture-plus-ID framing makes the distinction from a list tool obvious.

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 clause 'so you can diagnose and fix it with precision without guessing' gives a clear use context: pull this when you need to root-cause and fix a reported defect. No when-not conditions or explicit alternatives are given, so it falls short of a 5.

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