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

With no annotations, the description carries the full behavioral burden. It usefully discloses a rate limit (20/day), the optionality and length cap of details, and that only approved apps are reportable, but says nothing about required auth (api_key vs Bearer), whether a report is reversible, or what happens after submission.

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 covering purpose, exclusion, optional parameter bound, and rate limit. Slightly wasteful in re-listing all seven enum values that the schema already enumerates.

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 simple report-submission tool with no output schema, the description covers purpose, scope (approved apps only), reason set, details cap, and rate limit. The main uncovered gap is auth/permission expectations around the optional api_key parameter.

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 documents slug, reason, api_key, and details. The description only restates the reason enum values and the 1000-character details cap, adding no semantics beyond the schema; 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?

States a specific verb (report) and resource (an approved app), and enumerates the exact reasons accepted. The phrase 'approved app' scopes it and, together with 'not a low score', separates it from siblings like vote or write_review without needing the schema.

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 says when to use it ('rule violations') and when not ('not a low score'), which routes the agent away from review/vote tools. It does not name the alternative sibling to use for a low score, so it falls just short of fully explicit routing.

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