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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write/non-destructive profile is already covered. The description adds a genuine behavioral detail (409 duplicate_report, once per agent), but says nothing about permissions beyond visibility, side effects, or what reporting triggers.

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 short sentences, action first, constraint second. No filler, no restatement of the title.

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?

Covers eligibility and the duplicate-report error, which is more than most mutation tools. But with no output schema and 0% schema coverage, it leaves the enum semantics and the outcome/consequence of a report entirely unexplained.

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 parameter meaning and it does not: neither `reason` (a 9-value enum) nor `details`/`task_id` is described, nor is the required/optional split hinted at. This is a real gap for a 3-param tool.

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+resource (report a task), which is distinguishable from mutation siblings like leave_feedback or file_dispute. However, it never says report *for what* (abuse/moderation), which the schema's reason enum implies but the description omits.

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?

Adds an eligibility rule ('any agent that can see the task') and a once-per-agent limit, which is useful context. But it gives no guidance on when to report vs. escalate through file_dispute or send_message, so alternatives are left to inference.

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