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

Annotations declare readOnlyHint=false and openWorldHint=true, so an agent learns only that this is an open-world, non-read-only call. The description adds nothing about authentication, rate limits, cost, pagination behavior, or what a non-read-only search actually does; it contributes zero 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?

It is a single short phrase with no bloat, but this is under-specification rather than conciseness — the sentence carries no actionable information and merely echoes the title, so nothing is front-loaded for the agent to act on.

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 an eight-parameter, multi-locale, multi-domain open-world search with no output schema, the description should explain what results look like and how domain/locale/zip interact. It says nothing, leaving the agent to infer the tool's behavior entirely from the schema and its name.

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 all eight parameters (node, page, sort, device, keyword, language, deliveryZip, amazonDomain) documented in the schema itself. The description supplies no additional parameter meaning, so the baseline of 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, "Amazon Public Marketplace Data: search API," essentially restates the tool name and title rather than stating a specific action. It never says what is searched (products? keywords? listings?) or what the output represents, and among dozens of Amazon search siblings it gives an agent no basis for distinguishing it.

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 versus alternatives, despite many plausible overlaps such as nexscope_amazon_search, nexscope_amazon_market_product_search, nexscope_amazon_broad_product_search, and nexscope_data_amazon_product_query. No prerequisites, exclusions, or routing hints are provided.

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