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

Annotations already declare the safety profile (readOnly=false, destructive=true, openWorld=true, idempotent=false). The description adds genuinely non-obvious behavior: that the call consumes paid SEO add-on credits and requires top-up. It does not explain result size, pagination, or why a 'read'-looking analysis is marked destructive, but the credit-cost disclosure is real added value.

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?

Front-loads what it does, then why it matters, then the parameter, then cost. Zero filler sentences, though the 'Why it matters' passage is slightly long for a tool description. Well structured and scannable.

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 no explanation, and the description covers purpose, use cases, the key parameter variant, and credit cost. Only gaps are the undocumented limit/refresh parameters, which leaves the definition slightly incomplete for a 4-parameter tool.

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. It explains network_type well ('ip' = exact host, 'subnet' = /24 block that catches distributed networks) and implies target is a domain, but limit and refresh are never mentioned in either the schema or the description.

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?

States a specific verb and resource — groups linking domains by referring IP/subnet — and immediately distinguishes itself from generic backlink tools (seo_backlinks, seo_link_intersect) by framing the output as a private-blog-network signal. An agent can tell exactly what this returns 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 concrete when-to-use scenarios (before buying links, trusting competitor numbers, documenting negative-SEO attacks) tied to the analytical meaning of shared IPs. It stops short of naming alternatives or stating when NOT to use it, so it is strong but not fully routing.

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