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

Annotations already cover read-only/idempotent safety, so the description's job is added context — and it delivers the theme taxonomy, the sector dimension, and the 'which apps get it most' output shape. It does not mention anything about pagination or result limits, which is the only real gap.

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?

Purpose is front-loaded in the first sentence, then the dense theme lists follow, which is the right ordering. The enumeration is long but each entry is load-bearing since the keys are arbitrary shorthand that cannot be guessed.

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?

There is no output schema, so the description must convey return shape — and it does: frequency overall, frequency by sector, and top apps per theme. Combined with the full theme key vocabulary for both markets, an agent has everything needed to call this correctly.

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%, but the schema only says 'theme key or words, e.g. login, ads, refund, crash' — the description adds the complete enumerated key list for each market with human-readable glosses, which is information an agent could not derive from the schema alone. The market parameter's two modes are also explained.

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 opening sentence gives a precise verb-and-resource framing: frequency of a complaint theme in 1-star reviews, broken down overall, by sector, and by top apps. This is clearly distinct from get_app_complaints (per-app complaints) and estimate_one_star_cost, and the two-market split is stated up front.

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?

The final line, 'Omit theme to get the ranking of all themes,' gives explicit conditional guidance for the optional parameter, and the per-market theme vocabularies tell the agent which values are valid in which mode. It stops short of naming siblings as alternatives, but the usage context is unambiguous.

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