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

With no annotations, the description carries the full burden. It usefully discloses the data source, that results include rating counts alongside individual reviews, and that the app can be referenced by id or URL. It says nothing about pagination/limit behavior, rate limits, or country scoping effects, which matter for a 100-default limit.

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 clauses: what the resource is and what it contains, then a one-line usage hint. Front-loaded and free of padding, though the usage hint is thin relative to the space it takes.

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?

An output schema exists, so return-field explanation is not required and the description is spared that burden. What remains missing is sibling differentiation and semantics for three of four parameters — gaps an agent will hit when choosing between app_store_search and this tool or tuning country/sort.

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%, so all four parameters rely on the description. It clarifies that `app` accepts either an app id or a store URL, but leaves `sort`, `limit`, and `country` entirely unexplained (no allowed values, no max limit, no country code format).

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 names a specific resource (user reviews of an iPhone/iPad app from the Apple App Store) and states the alternative inputs (app id or store URL) plus the fields returned. It does not distinguish itself from siblings like app_store_details or app_store_search, so an agent must infer which one fetches reviews.

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 to analyse app feedback" gives an implied use case but no explicit when-to-use versus app_store_search (to find the app) or app_store_details (for metadata). No exclusions, prerequisites, or routing guidance are provided despite three closely related siblings.

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