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

Annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) only mark it as a non-destructive external write; the description adds the key behavior that the claim is hidden from *new* retrievals pending operator review, which is genuinely new information. The privacy constraint ('without private information') adds a further operational rule. It still doesn't say whether the report is reversible by the reporter or what feedback the caller receives.

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?

Two tight clauses with the effect stated immediately after the action, and the privacy constraint last. No filler or restatement of the name.

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 three-required-parameter write tool with no output schema, the description covers purpose, side effect, and reason hygiene, which is a solid base. It leaves open what the caller gets back, whether self-reports are allowed, and what happens to already-returned results, so it is adequate rather than 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 coverage is 33%: only agentKey is described in the schema, while id and reason have no field-level descriptions. The description partially compensates by constraining reason content ('explain the specific issue without private information') and implying id refers to a previously retrieved claim, but it adds nothing about the reason length bounds or the reporting session key.

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 gives a specific verb and resource ('Report a retrieved claim as incorrect or conflicting') plus the concrete effect ('hide it from new retrievals pending operator review'). That effect plausibly separates it from retract_knowledge, but the sibling is never named, so an agent must infer the distinction.

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?

'Report a retrieved claim as incorrect or conflicting' states the triggering condition clearly, and the pending-review framing tells the agent this is a soft flag rather than a permanent removal. It does not explicitly say when to prefer retract_knowledge or contribute_knowledge instead, nor what happens on a duplicate report.

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