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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing on top of that — no cost, rate limit, data-freshness, or pagination behavior for what is evidently a paginated snapshot query.

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?

The single sentence is short but is pure under-specification rather than concision — it is a title echo that conveys no information beyond the tool name already shown to the agent.

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 13-parameter, zero-required, open-world query tool with no output schema and dozens of overlapping Amazon siblings, the description supplies none of the context needed (what dimensions are returned, how filters combine, what defaults imply, which sibling to prefer).

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%, including the nested `order` object and enum-like value lists for `marketplace`, `matchType`, and `dataSnapshotMonth`, so the schema carries full parameter meaning. The description contributes no additional semantics; 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?

The description restates the title verbatim: 'Amazon Intelligence SS: competitor lookup API.' It names a resource ('competitor') but supplies no verb or scope beyond the name, and it gives no basis for choosing it over the near-identical sibling nexscope_amazon_competitor_lookup or over search-ish siblings like nexscope_data_ss_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 at all: no preconditions, no exclusions, and no mention of the many overlapping Amazon competitor/search tools in the sibling list. An agent must guess at selection.

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