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

Annotations already declare `readOnlyHint: false` and `openWorldHint: true`, so the description does not need to repeat basic safety hints. It adds useful domain scope by naming the first 3 pages, 30-day exact search volume, median PPC bid, and TOP3 ASIN data, but it says nothing about auth requirements, rate limits, data freshness, or what the `readOnlyHint: false` annotation means for this analysis tool.

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 first sentence is front-loaded and informative, but the trigger list is excessively long and repeats terms such as 'PPC bid analysis', 'search result brand distribution', and 'competitive landscape'. The repetition bloats the description without adding discriminating guidance.

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?

Given a simple two-parameter schema and no output schema, the description provides enough output-scope context for an agent to understand what will be returned. It is missing sibling differentiation and output-format expectations, but it is otherwise complete for this analysis tool.

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% for the two parameters, and the schema already documents `keyword` and `marketplace` with examples and allowed marketplace codes. The description does not add any parameter-level guidance beyond what the schema provides, so baseline 3 is appropriate.

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 clearly states a specific analysis resource and scope: keyword Share of Voice for Amazon, covering first-3-page visibility split, search volume, PPC bid, TOP3 ASIN metrics, and 10 marketplaces. It is clear what the tool does, but it does not explicitly distinguish itself from the similarly named sibling `nexscope_data_js_keywords_share_of_voice` or nearby keyword-intelligence tools.

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?

It gives an extensive list of user trigger phrases and explicitly says to trigger even when the user does not name Share of Voice. That is strong when-to-use guidance, but it does not state when not to use the tool or name alternatives such as other keyword or competitive-analysis siblings.

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