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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description does add real cost context (usage-based billing, ~$0.02 default estimate, settlement may differ), which is genuinely useful for an agent, but says nothing about auth, latency, or 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?

It is short, but it is short because it omits its actual job — the only sentences present are a cost disclaimer. Brevity without any statement of purpose is 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?

An output schema exists so return values need not be explained, but for a networked, billed search tool the description supplies no purpose, no parameter meaning, and no usage routing. It is wholly inadequate despite the output schema.

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% and the description never mentions 'phrase' (the required keyword) or 'database' (the market selector). With two undocumented parameters and no compensating text, the agent has no basis for supplying them.

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 only a pricing/billing banner and never states what the tool does. There is no verb or resource ('fetch SEMrush organic search results'), so an agent must infer everything from the tool name alone and cannot distinguish it from get_semrush_paid_results.

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 prerequisites, and no routing to alternatives such as get_semrush_paid_results or the DataForSEO organic SERP siblings. The only content is billing information.

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