Get App Reviews

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

The readOnlyHint and openWorldHint annotations already indicate a safe read operation. The description adds minor context about pagination ('a page') and sorting ('recent or helpful'), but does not disclose requirements like needing either id or appId, or country defaults. This is a modest addition beyond annotations.

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 a single, clear sentence that immediately conveys the tool's purpose. It is well-front-loaded and contains no redundant information, making it highly concise and easy to parse.

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?

Given the presence of an output schema and full parameter descriptions, the description is largely complete. It effectively communicates the core purpose, but it could benefit from noting that reviews differ from ratings (given the app_store_ratings sibling) or specifying that either id or appId is required. Overall, it is adequate for a simple read-only tool.

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%, with all six parameters described. The description's mention of 'recent or helpful' aligns with the sort parameter but adds no new semantic meaning beyond the schema. It neither clarifies the id/appId relationship nor parameter constraints, so it meets the baseline without exceeding it.

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 clearly states the tool fetches a page of App Store reviews, with 'page' and 'recent or helpful' indicating pagination and sorting. However, it does not explicitly differentiate from the sibling tool app_store_ratings, which could cause confusion about scope (reviews vs ratings).

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 implies usage when you need app reviews but provides no explicit guidance on when to use this tool over alternatives like app_store_ratings or app_store_search. There are no exclusions or alternative tool mentions, leaving some ambiguity in tool selection.

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