Get App Ratings

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

The description adds the output shape (histogram) but does not disclose additional behaviors beyond what annotations already cover. The readOnlyHint indicates a safe read, and openWorldHint suggests variable results, both provided by annotations. With annotations present, the description does not contradict or significantly extend them.

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, concise sentence that immediately communicates the tool's purpose. It contains no extraneous details, making it optimally front-loaded and easy to parse.

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 tool with a well-defined schema and output schema, the description is sufficient. It clearly states what the tool returns, and the schema covers parameter details, so an agent has all necessary context to use it correctly.

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?

The input schema already provides detailed descriptions for both parameters (id and country) with 100% coverage. The description adds no extra parameter context, so it meets the baseline but does not exceed schema documentation.

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's function: retrieving an app's total rating count and its 1-5 star histogram. It uses a specific verb ('Get') and resource ('an app's total rating count'), and it stands out from siblings like app_store_reviews by focusing on aggregate ratings rather than 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?

No guidance is provided on when to use this tool versus alternatives. The description implies its use for rating summaries, but it does not explicitly mention alternatives or when to prefer this over app_store_reviews or app_store_app.

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