get_app_reviews

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

With no annotations, the description must disclose behavioral traits. It states it reads reviews (read-only), pages, and orders newest first. It does not mention rate limits, authentication, or empty results, but the core behavior is clear. This is adequate, not exhaustive.

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 sentences, each earning its place: the first defines purpose and ordering; the second adds filtering guidance. No superfluous words, and key information is front-loaded.

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?

Without output schema, the description could optionally mention return structure, but it covers the essential aspects: what it reads, filtering, paging, and ordering. Given the tool's simplicity, it is fairly complete.

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%, baseline 3. The description adds value by giving concrete examples for the rating parameter (e.g., complaints, churn reasons). This enhances understanding beyond the schema's generic description.

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 verb 'Read' and the resource 'individual reviews for a Shopify app', and specifies ordering 'newest first'. It distinguishes from siblings like search_apps and get_review_summary by focusing on individual 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?

The description provides context for using rating filters with examples (e.g., rating=1 for complaints, rating=5 for positive). It does not explicitly state when to use this tool versus siblings, but the examples imply usage for sentiment analysis. The schema note about using search_apps first is helpful.

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