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 only real contribution is the pricing disclosure ($0.004 per successful request), which is genuinely useful cost context, but the description says nothing about what the call does, what it returns, or any 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?

The text is short and cleanly formatted, but it is entirely off-topic relative to the tool's function; every sentence is about pricing rather than the operation. Brevity here reflects missing content, not efficient writing.

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-value explanation is not required, yet the description omits purpose, usage context, and parameter meaning for a live external-API tool. It is not remotely complete for an agent to select and invoke it.

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 coverage is 0% and the single required parameter 'target' has no description anywhere. The description does not clarify whether 'target' is a domain, URL, or path — the one piece of information that would most help an agent invoke this correctly.

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 no functional statement at all — it is purely a pricing notice. Nothing tells the agent that this tool returns a Semrush backlinks overview for a target, nor how it differs from siblings like get_semrush_backlinks or get_semrush_referring_domains.

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 prerequisite information, and no reference to any alternative among the many sibling backlink tools. The agent has to infer applicability from the tool name alone.

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