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

Annotations already declare readOnlyHint=false and openWorldHint=true, but the description adds nothing beyond the label. It does not explain that a remote marketplace call is made, what permissions/credits are consumed, or why a 'query' is flagged non-read-only — leaving the readOnlyHint=false essentially unexplained.

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 one short sentence, but brevity here comes from under-specification rather than efficiency — there is nothing front-loaded because there is essentially no content beyond repeating the tool's title.

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 four required parameters, no output schema, and no return-value documentation, the description should at minimum say what estimate data comes back (units/revenue, granularity, historical vs projected). It says none of that, leaving an agent unable to predict the result of a call.

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%, with each of the four required parameters (asin, marketplace, startDate, endDate) documented in the schema including date format and a constraint on endDate. Per the high-coverage baseline the schema carries this dimension, and the description adds no extra meaning such as default date-window behavior.

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: sales estimates/query API') without stating a distinct verb, what the sales estimate actually measures, or what the caller gets back. It names the resource (sales estimates) but is effectively a tautology rather than a statement of function.

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 tool, and notably a sibling named nexscope_amazon_sales_estimates exists, yet the description never distinguishes the two or indicates when the query/date-range variant is preferred. No prerequisites, no exclusions, no alternatives.

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