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

Annotations declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, which is surprising for what the description portrays as a pure score lookup. The description never addresses safety, permissions, cost, or rate limits, and never reconciles the destructive annotation with the read-only-sounding behavior. It does add one useful behavioral fact — data is real-time for the date of the request and scored 0–1000 — but that is not enough to cover the gap. (Not scored as a hard contradiction because the description never explicitly claims read-only behavior.)

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 core capability and the score definition are front-loaded and the sentences are individually clear. The PageRank comparison and the help-center reference are filler that could be cut, but the text is not bloated overall.

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, and the description does define the rank scale's meaning. However, it omits target formatting rules, the rank_scale parameter's effect, and any indication of how this differs from the many sibling bulk endpoints, leaving real gaps for an agent deciding whether and how to call 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?

Top-level schema description coverage is 0% and the description adds almost nothing about inputs: it names the targets array but gives no format rules (no https:// or www for domains, absolute URLs for pages, 1000-target cap), and it never mentions the rank_scale switch between 0–100 and 0–1000. Since the description must compensate for the low measured coverage and does not, a 2 is appropriate.

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 states a specific verb and resource: it returns rank scores for domains, subdomains, and pages supplied in the targets array, and explains what the score measures (referring domains). That clearly separates it from siblings like bulk_backlinks_live or bulk_spam_score_live. It falls short of a 5 only because it never explicitly names a contrasting sibling or the condition that selects this one over them.

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 at all: no mention of the alternative bulk endpoints, no note that this is a live/real-time call versus a task-based one, and no prerequisites. The 'learn more in this help center article' pointer is external documentation, not in-definition guidance.

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