App reviews

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds a useful bound on result volume ('up to 10 pages of ~50 reviews'), but says nothing about ordering of the returned data, whether reviews are filtered/truncated, or what a page object contains.

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 short sentences, zero filler, with the core action first and the identifier requirement second. Nothing could be removed without losing 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?

For a simple read-only listing tool with full schema coverage and safety annotations, the definition covers purpose, volume bounds, and identifier requirements. The main remaining gap is that, with no output schema, the shape of a returned review is never described, but this is a modest omission for a well-understood resource.

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%, so the baseline is 3, but the description adds one genuinely new constraint: at least one of `id` or `appId` must be supplied, which the schema does not enforce (zero required parameters). That goes beyond the per-field docs and prevents a call with no identifier.

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 ('Get a page of user reviews for an app') and bounds the result volume (up to 10 pages of ~50 reviews). It is clearly distinct from siblings like app_ratings or app_details by naming the resource type, though it never explicitly contrasts with them.

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 only guidance is the selection rule between the two identifiers ('Provide either `id` or `appId`'). There is no indication of when to prefer this over app_ratings or app_details, nor any note on when paging past page 1 is worthwhile, so usage is implied rather than stated.

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