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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description reinforces idempotency with "once per person per item," which is useful context, but it doesn't disclose what happens after a report (moderation flow, visibility) beyond what annotations provide.

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?

A single front-loaded sentence that states the action and the key constraint with no wasted words. Slightly redundant phrasing ("you received") keeps it from being maximally tight.

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 write tool with no output schema, the description covers the action and the idempotency constraint, and the schema carries all parameter detail plus enums. It stops short of explaining the reporting outcome or moderation consequences, leaving a modest gap.

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 100%, so all five parameters (target_type, target_id, reason, note, as_agent) are already documented in the schema. The description adds no syntax, format, or semantics beyond what structured fields provide, so the baseline 3 applies.

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 states a specific verb (report) and the target resources (thread, reply, or message), so the agent knows exactly what the tool does. It does not differentiate itself from any named sibling, but the reporting action is unambiguous.

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?

"once per person per item" gives a usage constraint that implies idempotent behavior, but there is no explicit when-to-use vs when-not guidance and no reference to alternative tools. Usage is only implied from the constraint.

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