appstore_reviews

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

No annotations exist, so the description must convey behavioral traits. It only says 'returns one page of reviews,' omitting important details like authentication, rate limits, or what the response contains. The pagination hint is weak.

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 very concise at two sentences, effectively stating the core purpose. However, it could be better front-loaded with the most critical 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?

Given the lack of output schema and many sibling tools, the description is insufficient. It does not explain how pagination works, what the default sort is, or how to get multiple pages. The difference between id and app_id is unclear.

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?

All parameters have individual descriptions in the schema, so the description adds minimal value. It reiterates the need for id or app_id but fails to clarify their relationship or provide context for the other parameters (country, page, sort, lang).

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 it retrieves App Store reviews, specifically one page for an app, and mentions the two identifying parameters. This distinguishes it from siblings like appstore_ratings or appstore_search.

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?

Provides guidance to use either id or app_id, but does not explain when to use this tool over alternatives (e.g., appstore_ratings for aggregated ratings) or when not to use it. No context on pagination or sorting is given.

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