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

Annotations already flag destructiveHint and idempotentHint, but the description goes well beyond them: it states exactly which artifacts are destroyed, that the withdrawn text is not restored, and that a later re-approval surfaces as a brand-new comment rather than reviving the old one. That irreversibility and identity-change detail is the kind of context annotations cannot carry.

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?

Three sentences, front-loaded with the trigger condition, then effects, then consequences. No filler, no restating of the title beyond what the effects require.

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 destructive mutation with no output schema and zero param documentation, this is close to complete: destruction scope, irreversibility, ownership, and follow-up handling are all covered. The remaining gap is post-call state — whether the report ID becomes unusable and what the tool returns — plus the untouched parameter semantics.

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 carries the burden — and it only partly does. The prose 'After the user explicitly asks' and 'Requires ownership' loosely conveys the confirmation intent behind the const-true `approved` flag, but neither parameter is named, and the meaning of the required `reportId` (which report, and how to obtain it) is never addressed.

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 names a specific verb (withdraw/remove) and resource (the installation report), then enumerates the concrete effects: public feedback removed, installation count removed, pending email follow-ups cancelled. It is clearly distinguishable from sibling tools such as cancel_installation_followup, which only touches follow-ups, and from prepare_/publish_installation_report.

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 an explicit gating condition ('After the user explicitly asks to withdraw this report') plus a prerequisite ('Requires ownership') and a forward path (approve a new report later). What it lacks is a direct pointer to the closest alternative — a sibling exists purely to cancel follow-ups without withdrawing, and that routing is left implicit.

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