appstore_ratings

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

No annotations are provided, and the description only states what is returned. It does not disclose read-only nature, authentication needs, rate limits, or potential side effects. For an unannotated tool, more transparency is expected.

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 a single sentence that front-loads the action and clearly states the output. Every word is necessary; no fluff.

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 explains the output (total count and histogram) but does not clarify parameter dependencies or default behavior. For a tool with 4 optional parameters, more context about how they interact (e.g., needing at least id or app_id) would improve completeness.

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?

Parameter descriptions in the schema already explain each field (id, lang, app_id, country). The description does not add meaning beyond the schema, but the schema coverage is 100%, so baseline score of 3 applies.

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 it retrieves the App Store ratings histogram, specifying the return includes total ratings count and the 1-5 star histogram. This distinguishes it from sibling tools like appstore_app (app details) and appstore_reviews (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 implies usage for fetching rating distribution, but lacks explicit guidance on when to use this tool versus alternatives (e.g., appstore_reviews for text reviews). No exclusions or prerequisites mentioned.

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