seo_competitor

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

With no annotations provided, the description carries the full burden. It clearly discloses the default return behavior (bucket totals), the effect of 'detail' levels on output (medium = capped lists, full = raw API response), and the shape of the short output. It does not mention side effects or prerequisites, but the read-only nature and output details are well explained.

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 description is two sentences, front-loads the main purpose, and then efficiently explains the behavior of the 'detail' parameter. Every sentence earns its place with no redundancy or filler.

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 the lack of output schema and annotations, the description does a good job explaining return values for 'short' and 'medium' detail levels. The 'full' level is only described as 'raw API response', which is somewhat vague, and no error conditions or prerequisites are mentioned. Still, the core behavior is sufficiently covered for an agent to invoke the tool correctly.

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 coverage is 100%, so the baseline is 3. The description adds valuable extra meaning by mapping 'detail' values to concrete output shapes (e.g., 'medium' yields capped keyword lists up to 50 per bucket), which goes beyond the generic enum description in the schema. It also clarifies that 'competitorDomain' is compared against the brand's coverage.

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 uses a specific verb ('Compare') and resource ('brand's keyword coverage against a competitor domain'), making the core purpose clear. It distinguishes from generic sibling tools by describing the bucket totals output, though it does not explicitly name an alternative such as 'seo_gap'.

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?

The description implies when to use the tool (whenever you need to compare keyword coverage versus a competitor) but provides no explicit guidance on when not to use it or which alternative tool to choose. The detail parameter is explained, but there is no comparison against sibling tools like 'seo_gap' or 'competitor_analyze'.

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