list_reviews

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds only the vague phrase 'Apple pagination', without saying whether 'next' is an opaque cursor, whether results are sorted, whether results are scoped to territories or ratings, or how to detect the end of the list.

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 single sentence is front-loaded and free of wasted words, which is good. However, the brevity reflects under-specification rather than economy, since key behavior for a four-parameter list tool is simply absent.

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?

No output schema exists, so return-shape expectations would have to come from the description and do not. For a read-only list tool this is a moderate gap rather than a critical one, since the agent can still call it with an appId and see what comes back.

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 0% across four parameters, so the description must carry the burden and does not. It never explains that 'next' is a pagination cursor, that 'limit' caps results at 200, or that 'rating' filters reviews by star value, leaving the agent to guess from bare property names.

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 states a specific verb and resource ('List customer reviews for an app'), which is clearer than the bare name. It does not distinguish this from the sibling get_review, so the list-vs-fetch boundary is left to inference.

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?

There is no guidance on when to call this versus get_review or get_review_response, and no mention of prerequisites such as needing an appId from list_apps. The only contextual phrase, 'with Apple pagination', hints at continuation but never explains when or how to paginate.

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