Paid Competitors

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only query, how API units are consumed, or whether results are paginated, and it says nothing about cost despite the schema hinting that row count drives unit spend.

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?

A single efficient sentence with the resource and return content front-loaded. It is terse rather than padded, though the brevity contributes to gaps elsewhere.

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?

With no output schema and no annotations, the description partially compensates by naming the return content (paid keywords, ad traffic estimates). It still omits the required 'domain' input expectation, unit-cost implications, and how it differs from the organic-competitor sibling.

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 67%: limit and database are documented inline, while domain is undocumented but self-evident as the target. The description adds no parameter detail beyond what the schema already conveys, which is the expected baseline when the schema does the heavy lifting.

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 resource (domains competing with the target in Google Ads) and the outputs it returns (common paid keywords, ad traffic estimates). The 'paid' qualifier distinguishes it from the organic semrush_domain_competitors sibling, though it never explicitly names that alternative.

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 guidance on when to use this tool versus semrush_domain_competitors, semrush_domain_paid_keywords, or semrush_domain_overview. The use case is only implied by the word 'competitors', leaving the agent to infer selection criteria from the name alone.

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