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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely non-obvious context: 'Merchant data: includes the reviewer's name, email, Shopify customer id and order id,' warning that PII flows back, plus 'Real time' freshness. It does not discuss result volume or pagination behavior, which for a 250-per-page list tool would be worth a mention.

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?

Three sentences plus the endpoint path, front-loaded with the resource and return contents before filtering details. Dense but each clause carries information; the field enumeration is long-ish but useful for deciding whether to call the tool at all.

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 9-parameter, read-only list tool with no output schema, the description covers what is returned, what can be filtered, the default moderation scope, and the PII implication – enough to call it correctly. The omission of pagination/volume guidance (next_page looping) is the main residual gap.

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 every parameter is already documented in the schema, including the status default, the sort enum semantics, and the next_page pagination hint. The description's parameter text ('Filter by product, star rating, status...') largely restates what the schema already says rather than adding syntax or edge-case meaning. Baseline 3 is appropriate when the schema carries the load.

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?

Opens with a specific verb+resource ('List product reviews of the store') and enumerates the data returned (rating, text, media, merchant reply, product, verified flag, AI highlights, country, moderation status), so the agent knows exactly what payload to expect. It is clearly distinct from loox_get_product_review (singular) by the plural/list framing, but it never explicitly contrasts itself with loox_list_store_reviews, which is the closest sibling.

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?

Gives actionable usage context for filters, notably 'status (default: published only; use pending to find reviews awaiting approval)' and the date-range and rating filters, which tell the agent when to reach for each parameter. It stops short of naming alternatives or exclusions (e.g., when to use loox_get_product_reviews_summary instead of listing everything).

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