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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine behavioral detail not in the structured fields: that results are paginated and that a has_more flag in the response signals termination — important since there is no output schema.

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?

Three short sentences, zero filler, with the resource and pagination model front-loaded before the sort guidance. Every clause carries actionable 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 six parameters, no output schema, and an openWorld read, the description covers intent, sort choice, and pagination termination, but says nothing about the shape of a review record, behavior when an app_id is invalid, or store/country effects on results. Adequate but with visible gaps.

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 100%, so baseline is 3, but the description adds real semantic value the schema lacks: it explains what each sort mode is actually good for rather than just listing the enum, and it clarifies offset's role in a paging loop.

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 'Paginated user reviews,' identifying the resource and its paginated nature, and the required app_id plus pagination guidance makes clear it returns reviews for one app. It is clearly distinct from siblings like search_apps, get_app and top_charts, though the retrieval verb itself is only implied by the fragment.

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?

Gives concrete selection guidance for the sort parameter ('recent is best for monitoring new feedback; sort=helpful surfaces the loudest complaints') and an explicit pagination loop ('page with offset and stop when has_more is false'). It lacks any explicit when-not or sibling-routing statement, but usage context is clear.

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