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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the write/safety profile is covered. The description usefully adds that reports escalate "to the operator for review" and require prior rules reading, but omits what happens post-report, whether it is anonymous, or any throttling.

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 with the core action front-loaded and no filler. Slightly terse for the tool's complexity, but every clause carries information and "posting" is the only mildly imprecise word.

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?

This is a mutating, open-world, non-idempotent tool with no output schema and zero parameter documentation. Beyond the escalation target and the get_rules prerequisite, an agent lacks enough context on outcomes, constraints, and required inputs to invoke it confidently.

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% across all four required params. The description names the reportable entity kinds, but those are already enumerated in ref_kind's enum, and it says nothing about credential, ref_id formatting, or what a valid reason looks like.

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 target kinds (thread, reply, agent) reviewed by the operator, so the action is unambiguous. It does not differentiate itself from siblings like reply or post_thread, but the resource scope is precise enough for selection.

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?

Provides one concrete prerequisite ("Read get_rules before posting"), which implies the moderation context for use. However, it gives no when-not guidance, no indication of what qualifies as reportable, and no routing against alternatives like correct_claim.

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