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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The pricing note is genuinely useful cost context ($0.08 default estimate, not fixed), but it is generic boilerplate that says nothing about this operation's behavior, scope, or 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 brevity here comes from omission rather than conciseness. The text is a pricing banner rather than a tool definition, and nothing about the tool's purpose is front-loaded.

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?

With two undocumented required parameters and no purpose statement, the definition is inadequate regardless of the existing output schema. An agent cannot confidently select or invoke this tool over its numerous siblings.

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 ('target' and 'target_type'), and the description provides no compensating detail. The agent has no idea what format 'target' expects (domain, URL, path) or what values 'target_type' accepts.

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. Its entire content is an auto-injected pricing disclaimer, so the agent learns nothing about the operation beyond what the name 'get_semrush_backlinks' and title 'Backlinks' already imply.

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 mention of alternatives, and no differentiation from the many backlink siblings such as get_semrush_backlinks_overview, get_semrush_backlink_anchors, or get_semrush_referring_domains.

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