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

Annotations declare readOnlyHint=false and openWorldHint=true, which contradicts the apparent read-only nature of a research/analytics query, and the description offers no clarifying context about cost, rate limits, or side effects. Beyond structured fields, the description discloses nothing behavioral at all.

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 short and front-loaded, but this is under-specification rather than conciseness: the single sentence is pure title boilerplate that earns no place as a description.

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 no output schema and an operation whose return shape (share-of-voice percentages, competitor breakdown, timeframe) is entirely unknown, the description omits everything an agent would need to judge fit before calling.

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 both parameters (keyword, marketplace with an enumerated market list) are fully documented in the schema. The description adds no extra semantics, but the schema 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 is a verbatim restatement of the tool title/name: 'Amazon Research JS: keywords/share of voice API.' It reveals no verb or operation — is it fetching, computing, or listing share-of-voice data? An agent learns only the product namespace and the data domain, nothing actionable.

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 zero guidance on when to use this versus the many close siblings, notably nexscope_amazon_keyword_share_of_voice, nexscope_data_js_keywords_by_keyword, or nexscope_data_js_keywords_by_asin. No prerequisites, no exclusions, no alternative routing.

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