keyword_universe

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

Beyond annotations (readOnly, idempotent), the description adds significant behavioral context: it requires DataForSEO/Google Ads configuration, is paid/optional, explains the provider chain for volume data, and warns about 2026 signal degradation. No contradictions with 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?

The description is concise and front-loaded with the core value proposition. Every sentence serves a purpose, covering the main function, competitive advantage, optional features, prerequisites, and a future caveat. No wasted words.

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 tool's complexity (paid, external, gap analysis, optional volume, no output schema), the description covers essential aspects: what it does, prerequisites, limitations. It lacks explicit return format details, but the description sufficiently implies the outputs (list of gap keywords or volume metrics).

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 baseline is 3. The description adds value by explaining how parameters relate to the core gap analysis (competitors, target_domain) and optional volume lookup (keywords), and sets expectations for limit. This enriches understanding beyond schema descriptions.

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 the tool provides external keyword data with a core value of competitor keyword gap analysis. It distinguishes itself from sibling tools by noting it uses DataForSEO and has no Google equivalent, making its purpose unique.

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 provides clear context for when to use this tool, highlighting its competitive gap functionality and optional volume data. It implicitly differentiates from Google-based tools by stating 'no Google equivalent' and warns about signal degradation, but could more explicitly state when not to use it.

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