report_user

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

Discloses that reports are irreversible ('cannot be withdrawn once submitted'), requires authentication ('app password'), and is subject to rate limiting. Annotations indicate destructive hint, which aligns with the description. No contradictions.

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?

Three sentences, each serving a distinct purpose: stating the action, providing usage context, and differentiating from sibling. No unnecessary words.

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?

Given the full schema coverage, annotations, and output schema, the description covers all necessary aspects: purpose, behavioral details, usage guidance, and differentiation. No gaps.

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 the schema already fully explains each parameter. The description does not add new information beyond what is in the schema, meeting the baseline for high coverage.

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?

Clearly states the action ('report a user account'), the resource ('account'), and the scope ('entire account'). Differentiates from sibling 'report_content' by specifying that this tool targets accounts, not specific posts.

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?

Explicitly provides when to use this tool ('report a user account') and when to use the alternative ('use report_content when the violation is limited to a specific post'). Also notes that reports are reviewed asynchronously and cannot be withdrawn.

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