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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description's only added value is a usage-based billing note ($0.02 default estimate), which is genuine cost context not present in annotations, but nothing is said about scope, database semantics, or result limits.

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?

It is short, but the content is an HTML-comment-wrapped billing banner rather than front-loaded task information. Brevity here reflects missing content, 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?

An output schema exists so return values need not be explained, but for a two-parameter query tool with 0% schema coverage the description supplies nothing an agent needs to invoke it correctly – no purpose, no parameter meaning, no usage context.

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 0% for two required parameters (domain, database). With no enums and no schema docs, the description must compensate, and it says nothing about expected domain format or valid database values.

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 contains zero functional content – it is entirely a pricing banner. The only signal about what the tool does comes from the tool name itself, and there is no differentiation from siblings like get_semrush_url_organic_keywords or get_semrush_organic_competitors.

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 when-to-use guidance, no alternatives named, no prerequisites. An agent has no basis for choosing this over the many other Semrush/DataForSEO keyword tools listed as siblings.

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