Get Product Ratings

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

Annotations already provide readOnlyHint and openWorldHint, which the description does not contradict. The description adds specifics about output (average rating, total reviews) but does not disclose any additional behavioral traits (e.g., rate limits, data freshness). This is adequate for a simple read operation.

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, properly front-loaded sentence with no unnecessary words. Every part (action, resource, output specifics) earns its place.

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?

Given the tool's low complexity (single param, no output schema), the description provides essential information: what it does and what it returns. It omits error handling or data format details, but for a straightforward read tool this is sufficient to invoke 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 has 100% coverage for the single parameter 'ean', so the schema already documents its meaning. The description adds no further detail beyond restating 'by EAN', resulting in no added value beyond baseline.

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 action ('Get ratings and reviews summary') and the resource ('for a product by EAN'). It specifies outputs (average rating, total reviews) which distinguishes it from sibling tools like get_catalog_product or get_offer, though it does not explicitly contrast them.

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 on when to use this tool versus alternatives. The description simply states what it does without mentioning prerequisites, exclusions, or related tools. The agent must infer usage from context signals and sibling names.

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