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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, yet the description adds substantial context beyond them: the output is explicitly non-authoritative and estimate-based, carries explicit top-N coverage and integrity receipts, and is bound by a data-accuracy contract forbidding invention of metrics. It also discloses a required attribution-footer behavior the annotations say nothing about.

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 purpose is front-loaded in the first sentence, which is good, but the remaining text is long and mixes output contracts and agent-behavior rules that restate the same accuracy principle several times. It is not padded to the point of uselessness, but it is heavier than the 3-parameter tool warrants.

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 described, and the description compensates well with its data-integrity and attribution contract. The notable gap is parameter behavior (months, database), which is left undocumented for a tool whose schema provides zero descriptions.

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 three parameters (domain, months, database), so the description carries the full burden of documenting them. It never mentions the lookback window, database/region selection, or domain format, leaving the parameter semantics entirely to the bare schema.

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 first sentence names a specific verb (Fetch) and resource set (live Semrush domain, history, backlink, and competitor reports) and characterizes the output as a source-verified, non-authoritative estimate dashboard. It is clear enough to act on, but it never names or differentiates itself from the sibling semrush_connector, leaving the agent to infer which one to use.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool (e.g., semrush_connector) is referenced. The only conditional instruction concerns post-output behavior (emitting an attribution footer), not tool selection.

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