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

Adds real context beyond the annotations: the SEO Intelligence add-on dependency and the fact that the call consumes credits. However, with readOnlyHint=false and destructiveHint=true declared, the description says nothing about why the call is considered non-read-only or destructive (e.g. what refresh does), leaving a behavioural question open.

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?

Purpose is front-loaded in the first sentence, followed by output contents, two use cases, and cost. It is slightly long, but each sentence adds decision-relevant value, so little is wasted.

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, and the description covers purpose, use cases, and cost. For a three-parameter call with 0% schema coverage the parameter documentation gap and the unexplained destructive annotation keep it from being complete.

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%, so the description carries the full burden, yet it never mentions target, limit, or refresh. The notion of a domain target is only implied, and limit/refresh semantics (pagination size, cache-bypass/credit impact) are entirely absent.

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?

Specific verb+resource: it states it returns the individual pages of a domain that attract links, with referring domains, authority and spam score per page. This clearly separates it from domain-level siblings like seo_backlinks and seo_backlink_list, and an agent can tell what it produces without opening the schema.

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?

Gives two concrete when-to-use scenarios (own domain for internal linking, competitor domain for content-idea discovery), which is strong contextual routing. It does not, however, name or exclude the closest sibling tools (seo_backlinks, seo_broken_backlinks, seo_link_intersect), so the agent still has to infer when this beats them.

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