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

Annotations only say it is a non-destructive, non-idempotent write with no open-world access; the description adds what actually matters — that filing has no side effect on results, that a report number comes back, that no reply arrives through the tool, that reports are human-read, and a privacy boundary on what may be included. Nothing contradicts readOnlyHint=false or idempotentHint=false; 'once per problem' in fact clarifies the non-idempotent behaviour.

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?

Four short paragraphs, ordered trigger → exclusions → content → side effects, with the core instruction front-loaded. The 'Not for' sentence is long but each clause prevents a distinct class of bad reports, so it largely earns its space.

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 7-parameter, 2-required write tool with no output schema, the description covers the trigger, the exclusions, how to fill the key fields, the privacy constraint, and what comes back (a report number, no reply). An agent has everything needed to file a useful report without asking further questions.

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 already 100%, so the baseline is 3, but the description goes further by telling the agent what content belongs in `tool`, `toolInput`, `observed` and `relatedIds` (task/record ids so exact runs can be inspected) rather than just their types. It stops short of covering `severity` levels or `title` examples beyond what the schema already states.

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 opening sentence names a specific verb and resource — file a bug report about this server's own tools — and scopes it to the operator team as recipient. No sibling tool does anything comparable, so the agent can place it immediately.

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?

It gives a concrete trigger list (error not caused by the request, wrong/incomplete result, hang, behaviour contradicting the description), an explicit exclusion list (empty search, missing page, hinted errors, user-answerable questions), and a frequency rule ('once you have actually seen it, and once per problem'). That is the full when/when-not/alternative triad.

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