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

Annotations provide only readOnlyHint=false and openWorldHint=true, and the description adds nothing about what the tool actually does, whether it consumes quota/credits, paging behavior, or result shape. It doesn't contradict annotations outright, but for a 32-parameter query tool it carries essentially zero behavioral information.

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?

It is a single short sentence, but its brevity comes from under-specification rather than efficiency — it contains no information an agent could act on. Nothing is front-loaded because there is nothing to front-load.

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?

With 32 parameters, no output schema, and annotations that only state openWorldHint/readOnlyHint, the description is grossly inadequate. An agent cannot tell what records come back, how 'needCount' paging interacts with the result set, or why a read query is marked readOnlyHint=false.

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 including ranges, sort syntax, category lists, and keyword limits is already documented in the schema. The description adds nothing beyond that, 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 restates the title verbatim ("Amazon Research JS: product database/query API") without adding a verb, scope, or unit of retrieval. It doesn't distinguish this from the many sibling Amazon product databases/search tools (nexscope_amazon_product_database, nexscope_amazon_product_database_search, nexscope_data_st_amazon_product_query). 'JS' is opaque jargon that an agent can't resolve without external knowledge.

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?

There is no guidance on when to use this versus any alternative, no mention of prerequisites (e.g. that marketplace is required), and no exclusions. The agent is left to guess from the parameter list alone in a cluster of near-identical Amazon product-database siblings.

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