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

With no annotations provided, the description carries the full burden of explaining side effects, permissions, or outcomes, and it discloses none. The phrase 'report abuse' does not reveal whether this is a one-way submission, whether it blocks content, notifies moderators, or has rate limits.

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?

The description is extremely short, but this is under-specification rather than useful conciseness. It provides no front-loaded context, no structure, and no information worth keeping.

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 tool with three required parameters, an enum, and no annotations or output schema, this description is far from complete. An agent cannot identify when to call it, what the parameters mean, or what end result to expect.

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% and the description adds no meaning to the three required parameters: entity_type, entity_id, and reason. The agent must infer from raw schema constraints, such as entity_type enum values, without any explanation of valid usage.

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 'report abuse' restates the tool name with no elaboration, making it essentially the same term rather than a meaningful statement of function. It does not clarify what kind of abuse is meant, what entities are reportable, or how this differs from neighboring tools like audit_citations.

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 guidance whatsoever about when to call this tool, what triggers a report, or which sibling tools to prefer. An agent is given no criteria for choosing report_abuse over other available tools.

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