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

Annotations declare readOnlyHint=false and openWorldHint=true, yet the description says nothing about authentication, data freshness, historical month coverage, or what a "traffic keyword" record contains. It neither confirms nor contradicts the annotations, so it adds no behavioral signal beyond them.

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 entirely wasted — it duplicates the title and front-loads nothing actionable. Brevity here reflects under-specification rather than efficiency.

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 11-parameter data query with no output schema, the description should at minimum explain what a result row is and how month/badges/type filters change it. It supplies none of that, leaving the tool effectively opaque.

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 11 parameters (asin, month, badges, orderField, trafficKeywordTypes, etc.) are already documented in the schema. The description adds no semantics on top, which lands at the baseline 3 for high coverage.

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 Intelligence SS: traffic/keyword API" restates the tool name and title without a verb or any statement of what data is produced. It does not distinguish this tool from the many near-identical siblings such as nexscope_amazon_traffic_keywords, nexscope_amazon_asin_traffic_summary, or nexscope_data_sf_asin_keywords.

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?

No when-to-use context is given at all: no mention of the reverse-ASIN lookup scenario, no exclusions, and no pointer to any of the many sibling keyword/traffic tools that overlap with it. An agent must infer everything from the parameter list.

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