gold_semrush_gap

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

With no annotations provided, this description carries the full burden of behavioral disclosure, and it does reasonably well. It warns that SEMRUSH_API_KEY is required, that the feature is paid-only at the PRO $29 tier, and that the tool fails closed without the key. The 'Steal: metehan777/semrush-mcp 16 MIT' line is confusing but references provenance rather than behavior.

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 core purpose and prerequisites are front-loaded and compact. However, the 'Steal: metehan777/semrush-mcp 16 MIT' sentence is cryptic and does not help an agent invoke the tool, and 'PAID ONLY PRO $29' is terse to the point of ambiguity. The description would be stronger without the distracting provenance line.

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?

The description covers prerequisites and fail-closed behavior, which is valuable. It does not, however, explain what the output looks like or how this tool relates to the similarly-named sibling gold_keyword_gap_scan. For a relatively simple two-parameter tool, it is minimally adequate but leaves room for clearer guidance.

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 the schema already documents both domain and competitor_domains. The description adds only a slight reinforcement of the 'up to 3' limit for competitor_domains, which is already stated. It does not provide additional meaning beyond the schema.

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 performs a Semrush keyword gap analysis between a primary domain and up to 3 competitor domains. This identifies both the resource and the scope of the operation. However, it does not explicitly distinguish itself from the sibling gold_keyword_gap_scan, so it falls short of full differentiation.

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 gives clear context: use this when comparing a domain's keyword gaps against up to 3 competitor domains. It also notes the SEMRUSH_API_KEY prerequisite and the fail-closed behavior if the key is missing. It does not explicitly mention alternatives or when not to use this tool.

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