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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds only a cost estimate (~$0.02, not fixed), which is genuinely useful context for a paid third-party API, but it omits auth needs, rate limits, and result shape.

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 text is short, but every line is irrelevant boilerplate about pricing rather than tool purpose. Brevity here reflects under-specification, not conciseness.

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?

Even granting that the output schema covers return values and annotations cover safety, the description omits the one thing only it can provide: what the tool returns and how it differs from its Semrush siblings. The definition is functionally incomplete.

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?

Two required parameters (url, database) with 0% schema description coverage, and the description supplies no meaning, format, or valid values for either. For a required 'database' field this is a real gap, as the agent cannot know whether it expects 'us', 'google.com', or a locale code.

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 never states what the tool does. It contains only a pricing banner, so the agent must infer purpose from the name alone, and nothing distinguishes it from sibling get_semrush_domain_organic_keywords.

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 about when to use this tool versus the many sibling alternatives (domain organic keywords, organic competitors, Ahrefs/DataForSEO equivalents). The only conditional text is about billing, not usage.

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