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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds nothing about authentication, rate limits, pagination caps, or cost. It also offers no hint of what a query returns, which matters since no output schema exists.

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 short sentence, so it is not bloated, but it also fails to earn its place by conveying anything the tool name does not already say.

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 six-parameter query tool with conditional logic (queryMode 1 vs 2), a 1-16 queryType enum referenced by a table that is absent, and no output schema needs real explanatory context. The description supplies none, so an agent cannot use queryType correctly from the definition alone.

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 six parameters including queryType and queryValue are documented in the schema itself. The description contributes no additional semantics, 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?

"Amazon Research ST: amazon/product Query API" restates the tool name and title without adding a verb, resource scope, or outcome. An agent cannot tell from this what is actually queried (products? by ASIN, keyword, category?) or how it differs from nexscope_amazon_product_search or nexscope_data_st_amazon_product_detail.

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, when-not-to-use, or alternative recommendation anywhere in the description. With hundreds of Amazon product siblings in the toolset, the absence of any routing guidance leaves selection entirely to guesswork.

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