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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered externally. The description adds nothing beyond that — no mention of pagination limits, per-star caps, rate limits, or that only one ASIN per request is allowed (that fact lives only in the schema).

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 fragment that is technically brief but conveys almost no information; brevity here is under-specification rather than conciseness. There is no front-loaded statement of action or scope to anchor the agent.

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 12-parameter tool with no output schema, the description must carry meaningful burden about what a call yields and how the many filters interact (star counts, reviewer type, media type, domain). It supplies none of this, leaving the definition inadequate for correct invocation.

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 all 12 parameters (asin, sortBy, star1Num–star5Num, mediaType, domainCode, formatType, reviewerType, filterByKeyword) are documented in the schema itself. The description contributes no additional meaning, 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 is a restatement of the title and tool name ('Amazon Public Marketplace Data: reviews/list API') with no verb, no scope, and no statement of what is returned or which product entity is targeted. An agent can infer it lists reviews for an ASIN only by reading the schema, not the description.

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 when-to-use, when-not-to-use, or alternative mentioned, despite many siblings that overlap (nexscope_amazon_niche_reviews_by_keyword, nexscope_amazon_reviews_list, nexscope_amazon_product_detail). Nothing routes the agent between them.

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