appstore_ratings

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

Description accurately states behavior (retrieves histogram, returns count and star distribution). No annotations exist, so description carries full burden; it is clear but could mention that it is a read-only operation and any rate limits or prerequisites.

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 succinct sentences that are front-loaded with the action and output. Every sentence adds value with no redundancy or 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?

Description covers the retrieval of histogram data well. However, it does not specify behavior when no parameters are provided (all are optional) or default results. Still adequate for a simple read tool.

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% (all 4 parameters documented in input schema). Description does not add extra meaning beyond what the schema already provides (e.g., id, app_id, country, lang). Baseline score of 3 is appropriate.

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?

Description clearly states the tool retrieves App Store ratings histogram and specifies the output (total count and 1-5 star histogram). It distinguishes from sibling tools like appstore_reviews and appstore_app by focusing on histogram data.

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?

No explicit guidance on when to use this tool versus alternatives. Usage is implied through the description, but no 'when not to use' or comparison to siblings like appstore_reviews or appstore_app is provided.

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