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 externally. The description adds nothing on top of that: no note on data freshness, marketplace coverage implications, rate limits, or what a "share of voice" result represents. It neither contradicts nor enriches 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 sentence, but it is short because it carries no content rather than because it is well-edited. The only text present duplicates the title verbatim, so there is nothing to be concisely structured around.

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 two-parameter read-only analytics call with no output schema, the description should at minimum explain what share-of-voice metric is computed and over what set of competitors. Instead it is silent on inputs beyond the schema and on the meaning of the result, leaving the agent to guess the tool's function from its name alone.

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% and both parameters (keyword, marketplace) are documented inline including the allowed market codes. The description contributes no additional meaning about keyword format, multi-keyword support, or marketplace defaults, so the 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 name/title ("Amazon Research JS: keywords/share of voice API") without a verb or any explanation of what the tool actually returns. It hints at a resource (share of voice for keywords) but adds no information beyond the identifier, so an agent cannot distinguish it from near-duplicate siblings such as nexscope_amazon_keyword_share_of_voice or nexscope_data_js_keywords_by_keyword.

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, when-not-to-use, or alternative-selection guidance of any kind. With multiple near-identical keyword/share-of-voice tools in the sibling list, the absence of routing guidance is a real selection failure, not merely an omission.

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