Organic Competitors

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

With no annotations, the description carries the full burden, and it discloses almost nothing behavioral. It never states that this is a read-only metered API call, that results consume API units (only the schema's limit field hints at this), or how results are scoped to the database parameter.

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 front-loaded sentence with zero filler; the resource and its ranking dimensions come first. It is efficient but omits any routing or constraint information that could have earned the fifth point.

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 read-only list tool with three parameters this is minimally adequate: the output dimensions are described, but nothing covers cost/API-unit consumption across the limit range, database scoping behavior, or why one would pick this tool over its many keyword/competitor siblings.

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 67%: limit and database are documented in-schema, domain is self-evident, and the description adds no parameter meaning at all. With coverage in the mid-range, the schema does most of the work, 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?

States a specific resource ('Domains competing with the target in organic search') and how results are ordered (competition level, common keywords, traffic). The 'organic search' qualifier implicitly separates it from the sibling semrush_domain_paid_competitors, though no sibling is named explicitly.

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?

No guidance on when to choose this over semrush_domain_paid_competitors, semrush_domain_organic_keywords, or semrush_domain_overview. Nothing states prerequisites, that domain is required, or when the tool is inappropriate.

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