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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description's only contribution is cost context ($0.08 estimate, usage-based billing, settlement may differ), which is genuinely useful but says nothing about what the call returns, its latency, or its external-data dependencies.

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 brevity here reflects omission rather than conciseness. The only content is a boilerplate pricing banner wrapped in HTML comments, which wastes the entire description budget on non-purpose information.

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?

Although an output schema exists (so return values need not be explained), the tool has a required parameter at 0% schema coverage and no stated purpose. For a 2-parameter keyword lookup with many near-identical siblings, the description is completely inadequate for correct selection or invocation.

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 both parameters ('phrase' and 'database'), and the description adds no meaning whatsoever about what 'phrase' should contain or what values 'database' accepts. With two undocumented parameters, the description fails to compensate for the gap.

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 an HTML-wrapped pricing notice ('Usage-based billing; Default request estimate: $0.08 USD'). Nothing identifies the resource (question keywords) or the verb (fetch), so an agent cannot distinguish it from the dozens of sibling keyword tools.

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?

There is no when-to-use guidance, no conditions, and no mention of alternatives such as get_semrush_broad_match_keywords or get_semrush_keyword_overview. The text provides zero routing information.

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