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

The description discloses important behavioral traits beyond the annotations: Apple's hard cap of 500 reviews, page limits (1-10), error on page>10, unsupported sort 'rating', and Google's token-based pagination with effectively unbounded results. These details are not present in the annotations and significantly enhance the agent's understanding of the tool's behavior.

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 compact, consisting of two sentences that front-load the core purpose and then efficiently detail platform-specific constraints. Every sentence provides useful information without redundancy, making it well-structured and easy to scan.

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 8 parameters and two platform variants, the description covers the key operational quirks and pagination details, which are the main sources of complexity. However, since there is no output schema, the description does not explain the return value structure (e.g., review fields), which slightly reduces completeness. Overall, it is nearly complete for the tool's purpose.

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?

The input schema covers 100% of the parameters with detailed descriptions, so the baseline is 3. The description adds some context (e.g., the aggregate cap of 500 per country, the RSS feed source), but most of the parameter-specific details are already in the schema. Thus, the description doesn't add substantial meaning 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?

The description opens with 'Reviews for one app,' which clearly identifies the tool's function: retrieving reviews for a single app. It distinguishes itself from sibling tools like get_app or get_app_permissions by focusing specifically on reviews, and the platform-specific details reinforce its unique scope.

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 description provides clear context on when to use the tool (for one app's reviews) and how to handle pagination differences between Apple and Google. It gives explicit usage tips like 'page>10 returns an error' and 'pass the nextToken from a prior call's pagination to page forward.' However, it doesn't explicitly name alternatives or state when not to use this tool, so it falls short of a 5.

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