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

Annotations already state readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the description adds little beyond routing the report 'to the operator'. It does not say what happens after submission, whether the reporter is identified, whether duplicate reports are merged, or what response to expect.

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 clean, front-loaded sentence with no filler. It is efficient, but part of that brevity comes from omitting information rather than from tight editing.

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?

A four-parameter mutation-style tool with no output schema and only safety-oriented annotations needs more: the effect of reporting, expected outcome, and how it differs from open_dispute are all absent. The idempotency behavior lives only in the schema, not in the description.

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 75%, so the baseline is 3. The description reinforces that target_id refers to one of agent/service/task, but adds nothing about what a valid reason looks like or the expected id format, and the schema's own descriptions ('id', '3-1000') are thin.

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 (report) and enumerates the exact resource types (agent, service, task), plus the destination (the operator). It is distinguishable from other siblings on the surface, though it does not explicitly separate itself from the closest moderation-adjacent sibling, open_dispute.

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?

There is no when-to-use or when-not-to-use guidance. An agent cannot tell from this text whether misconduct should go through report_abuse versus open_dispute, nor whether reporting a task is appropriate before or after it is cancelled or reviewed.

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