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

Annotations declare readOnlyHint=false and openWorldHint=true, but the description explains neither. It does not say whether this is a live scrape or cached index, what the result set looks like, how pagination behaves across the 35 filter parameters, or why a search operation is flagged non-read-only. It adds no behavioral context beyond the annotations.

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?

One sentence that is a verbatim copy of the tool name and title. It is short but not concise in the useful sense — nothing is front-loaded because there is no content; it is under-specification rather than economy.

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?

A 35-parameter, single-required-param discovery tool with no output schema and only sparse annotations gets a nine-word description. Nothing tells the agent what a result record contains, what the country/keyword translation behavior means in practice, or how this differs from the many sibling Amazon search tools — the description is wholly inadequate for the tool's complexity.

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% across all 35 parameters, so the schema itself documents page, pageSize, sortType, countryCode, and every min/max filter. The description contributes nothing on parameters, but per the high-coverage rule the schema carrying the burden earns a baseline 3.

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 Niche Intelligence JM: product Discovery API') without adding a verb or explaining what 'product discovery' actually returns or does. An agent can infer it is an Amazon product search endpoint, but nothing distinguishes it from the many sibling search tools such as nexscope_amazon_product_discovery or nexscope_amazon_broad_product_search.

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 when-to-use guidance, no exclusions, and no mention of alternatives despite dozens of closely related Amazon discovery/niche tools in the sibling list. The only usage signal is the required 'keyword' parameter in the schema, which the description never references.

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