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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral context on top: the compact-vs-full distinction, the fact that signed URLs only appear in full view (a data-exposure nuance), and the prompt-injection warning that the report body is untrusted user input wrapped in a boundary marker. That last point is exactly the kind of behavior an agent cannot infer from structured fields.

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 a single dense paragraph that is front-loaded with the core action and contents before moving to arguments and the safety caveat. Parenthetical-heavy phrasing and the trailing screenshot instruction make it slightly denser than ideal, but no sentence is filler.

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?

With no output schema, the description must describe returns, and it does so thoroughly via the enumerated payload and the compact/full difference. Gaps remain around pagination, size limits, and error behavior for an invalid eventId, but for a read-only fetch tool this is close to complete.

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 carry the load, and it largely does: it explains the provenance of projectId and eventId and clarifies what the 'view' enum actually changes. It stops short of 5 only because it doesn't state the parameter types or describe failure modes for a bad eventId.

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 ('Fetch a bug report') and enumerates the exact payload (ticket text, AI overview, runtime context, breadcrumbs, evidence, attachments), so an agent knows precisely what comes back. It names get_screenshot as the follow-up for images but never contrasts itself with close siblings like get_ticket or get_error_group, which is the only missing piece.

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?

Gives a clear routing rule ('To view an attached image, call get_screenshot with the artifactIndex') and states when the heavier view is warranted ('view=full expands samples and evidence'). It also tells the agent where the identifiers come from (list_projects or a report link), covering required inputs. No explicit exclusion of sibling report-fetching tools, so it stops short of 5.

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