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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's job is to add analytical scope, and it does: results are limited to the first 3 pages of search results, volume is a 30-day exact figure, bid is a median, ASIN data is TOP3 only, and coverage spans 10 marketplaces. It adds no cost/latency/auth or rate-limit context, which keeps it below a 5.

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 purpose and return metrics are front-loaded well, but the trigger sentence is a keyword-stuffed list with visible duplication: 'PPC bid analysis', 'search result brand distribution', and 'competitive landscape' each appear twice. Roughly a third of the text is redundant, which dilutes rather than sharpens routing signals.

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 analysis tool with no output schema, the description covers what is computed, the lookback (30 days), the ranking depth (3 pages), the marketplaces, and the trigger conditions. What remains unexplained is whether results are brand-aggregated or per-ASIN weighted by default (the 'weighted SOV' mention implies an option not exposed in the schema), and pagination/response shape.

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% — both 'keyword' and 'marketplace' are documented in the schema, with the marketplace options enumerated there. The description only alludes to marketplace scope via '10 marketplaces' and adds no format, normalization, or matching-behavior detail beyond the schema, so 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 names a specific analysis (brand Share of Voice in Amazon keyword search results) and enumerates exactly what it returns: visibility share across the first 3 pages (organic/ad/combined), 30-day search volume, median PPC bid, and TOP3 ASIN click/conversion data across 10 marketplaces. An agent can tell this apart from generic keyword tools like nexscope_amazon_keyword_overview. It stops short of naming the near-identical sibling nexscope_data_js_keywords_share_of_voice, so sibling differentiation is incomplete.

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?

Usage context is stated explicitly and generously: trigger on brand market share, brand voice share, ad slot share, PPC bid analysis, brand dominance, etc., plus an explicit fallback rule that it should fire even when the user never says 'SOV'. What is missing is any exclusion or alternative-tool guidance, particularly against nexscope_data_js_keywords_share_of_voice, which an agent would have no basis to prefer between.

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