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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: the data comes from the product page's curated reviews carousel and is a small, representative subset rather than a complete set, which meaningfully shapes expectations about result volume.

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?

A single dense sentence that front-loads the returned fields and follows with source and scope qualifiers. Every clause earns its place, though the sentence is long enough to be slightly taxing.

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?

An output schema exists, so return values need no explanation, and all three parameters are documented in the schema. The description covers scope, source, and content, leaving only minor gaps such as authentication or pagination expectations.

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%, so the schema already documents item_no, country, and language (including defaults). The description adds nothing about parameter syntax, formats, or country/language behavior, so the baseline 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 states a specific resource and scope: an IKEA item's highlighted reviews plus its aggregate rating, explicitly contrasted with 'the full paginated list.' It clearly defines what the tool returns, though there is no sibling IKEA reviews tool to differentiate from, and the verb is only implied.

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 phrase 'not the full paginated list' hints at when this tool is and isn't appropriate, but it names no alternative and gives no explicit when-to-use trigger or prerequisite (e.g. that you first need an item_no). Usage context is implied rather than stated.

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