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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful operational context: it is bounded/bulk, has no pagination, and unknown costs remain unapproved — but the billing/cost phrasing is cryptic and the "no new independent authority fact" sentence conveys no actionable 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 useful content (resource, bulk/bounded nature, no pagination) is packed into four clipped sentences, but two of them — "No new independent authority fact is claimed" and "Unknown costs remain unapproved" — are boilerplate that adds length without meaning for tool selection.

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?

For a single-parameter, no-output-schema tool the description should at minimum explain what a targetSpamScore is and what the bulk response contains. Instead it offers hedged, policy-flavored sentences while omitting return values, score scale, and per-target error behavior, leaving real gaps for an agent deciding how to use results.

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%, and the only parameter (targets: array of {kind: DOMAIN|PAGE, target: string}) is barely addressed. The phrase "domain and page" loosely maps to the kind enum, but the description never explains the max-20 bulk limit, the target string format (URL vs bare domain), or how the two kinds differ in output.

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?

"Bounded domain and page targetSpamScore values from the Nexscope backlink index" identifies the resource (spam scores) and the target types (domain/page), so an agent can infer the general purpose. However, it never says what a spam score is numerically (range, higher-is-worse), and it omits an action verb, leaving the purpose recognizable but vague.

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?

The description mentions an "independently callable bulk interface sharing source facts with backlink overview," which hints at a relationship to nexscope_seo_backlink_overview, but it never states when to call this tool instead of the overview or any other backlink sibling. No prerequisites or exclusions are given.

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