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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds crucial data-quality caveats beyond them: measured=false means absence of data rather than zero, provenance differs by platform (Steam sampled negative reviews, Roblox YouTube comments), and Fortnite coverage does not exist yet. Those are exactly the behavioral facts an agent needs before interpreting results.

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?

Very dense but front-loaded: output shape comes first, then scope, then data caveats, then usage. The opening two clauses are packed into a single comma-spliced sentence, which slightly impedes scanning, but no sentence is filler.

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?

Covers scope, return fields, sample-size semantics, per-platform source coverage, and intended use, while an output schema exists so return values need no further explanation. Nothing material for a correct call is missing.

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 coverage is 100%, so the baseline is 3, and the description still adds meaning: it explains that game, niche, and the implicit no-argument case ("all moving games") are alternative selectors rather than combinable filters. It does not address limit or cursor behavior, but those are fully documented in the schema.

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 the specific verb and resource (complaint themes with sharePct and sampleSize) and the three scoping modes (game, niche, all moving games). It is instantly distinguishable from siblings like get_game or analyze_niche, which return different data shapes.

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?

Gives a clear intended use ("Use the themes as angles for an original game that fixes them") and points to list_niches as the source for niche labels. It does not explicitly name when to prefer a sibling such as analyze_niche or get_gap_analysis instead, so routing is inferred rather than stated.

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