apps__customer_reviews__list

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds no behavioral traits beyond those; it mentions filtering and sorting which are already in the schema. It does not disclose pagination behavior, rate limits, or other operational details.

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 two sentences plus an endpoint hint, conveying essential information without unnecessary words. It is front-loaded with the core action and key attributes.

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?

The description covers basic usage but lacks details on pagination (next_url), response structure, and relationship includes. With no output schema, agents may need more context to properly invoke the tool. The schema fully documents parameters, but the description could better explain the pagination pattern.

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 baseline is 3. The description highlights the most common filters (rating, territory) and sort (-createdDate), adding value. However, it omits explanation of next_url pagination, include relationships, and other filters. Adequate but not exceptional.

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 the tool lists customer reviews for an app and mentions key features like filtering and sorting. It distinguishes from the sibling 'customer_reviews__get' (single review) and 'app_store_versions__customer_reviews__list' (version-specific) via the endpoint hint, but could be more explicit about the scope.

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 description gives usage hints (filter by rating/territory, sort by -createdDate) but does not explicitly state when to use this tool vs alternatives (e.g., version-specific review list) or when not to use it. Missing guidance on pagination or parameter conflict (next_url).

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