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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description still adds real behavioral context beyond them: that results can be scoped to a historical month and sorted along multiple dimensions, and which fields the keyword records expose. It omits pagination caps, rate limits, or auth/cost expectations.

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 core capability is front-loaded in the first sentence, with trigger conditions after it. The second sentence is a long, partly redundant word list ('traffic keyword list', 'Amazon traffic keywords', 'reverse ASIN keywords' overlap heavily), which costs some efficiency but does serve disambiguation.

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?

With 11 parameters, no output schema, and good annotation coverage, the description does enough to call the tool safely. However, it leaves the crowded ASIN-keyword/traffic-summary family undifferentiated and does not explain the referenced enum links (badges, trafficKeywordTypes), which are the trickiest inputs an agent must supply.

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 per-field notes on month format, page size limits, and the badge/traffic-type enums, so the baseline is 3. The description only echoes 'historical month' and 'multi-dimensional sorting' without specifying valid sort fields or enum values, adding little beyond the schema.

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?

States a specific verb and resource: query traffic keyword lists for an Amazon ASIN, enumerating the returned dimensions (traffic source type, conversion type, organic rank, ad rank). The purpose is clear, but the description never distinguishes it from near-identical siblings such as nexscope_amazon_asin_keywords, nexscope_amazon_asin_traffic_summary, or nexscope_data_ss_traffic_keyword, so an agent must still guess among them.

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?

Gives a rich set of trigger phrases ('ASIN reverse traffic keywords', 'keyword traffic structure', 'organic/ad keyword analysis') and explicitly says the tool applies even when 'Nexscope' is not named, which is genuine routing help. It stops short of exclusions or naming an alternative tool for the closely related ASIN-keyword and traffic-summary needs.

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