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

Annotations already declare read-only, idempotent and open-world access, so the description is free to focus on payload characteristics. It discloses the page size and the fields returned (rating/title/body/version/date/devReply/thumbsUp), which matters because there is no output schema. It doesn't mention the 10-page ceiling or Android-only sorting, but those appear in the schema.

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?

Two tight sentences: what it returns and where it fits in a workflow. It is front-loaded with the verb and resource, and every clause carries information.

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?

With no output schema, the field list compensates well, and usage context is supplied. Gaps are minor: the maximum page depth (effectively a result cap) and cross-store ordering differences are only implicit in the schema.

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% and every parameter including enums and defaults is documented there. The only parameter-adjacent detail in the description, '50 per page', restates the page field's schema text, so there is no value added beyond 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 a specific verb and resource ('Fetch raw app reviews') plus scope ('unified schema across stores') and enumerates the returned fields, which separates it from mine_app_pain_points. An agent can distinguish it from all siblings without opening 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?

'Use for drill-down after mine_app_pain_points' gives an explicit when-to-use and names the alternative it complements. It omits when-not-to-use (e.g. bulk collection, or that results are capped at 10 pages), so the routing guidance is clear but not exhaustive.

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