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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, and the description adds nothing beyond that — no mention of pagination limits (only in the schema), no note on historical vs real-time behavior, no coverage of marketplace-specific restrictions. With annotations present the bar is lower, but the description contributes zero additional context.

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 short, but that brevity reflects under-specification rather than efficiency: a single sentence that parrots the title earns no place and provides no front-loaded actionable information.

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 six-parameter tool with a multi-condition query mode, a 1-16 query type table, historical snapshot support, and no output schema, the description is wholly inadequate. An agent has no way to know what results to expect or how the two query modes differ without consulting the schema.

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%, and the schema itself thoroughly documents page limits, queryMode, queryType range, queryMonth format, and marketplace codes. The description adds nothing on top, so baseline 3 is appropriate since the schema carries the entire 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?

The description merely restates the title ('Amazon Research ST: amazon/product Query API') without naming a verb, the resource being queried, or what kind of query it performs. An agent cannot distinguish it from siblings like nexscope_data_st_amazon_product_detail or nexscope_data_amazon_product_research based on this text alone.

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, when not to, or which sibling to prefer for product queries. The only navigational signal is the parameter name 'queryType', which the description never explains.

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