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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description adds nothing to explain that profile — 'Unknown costs remain unapproved' hints at billing/pricing risk without saying what it means for the caller. Statements like 'No new independent authority fact is claimed' are internal-policy boilerplate rather than behavioral information an agent can act on.

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 several sentences ('No new independent authority fact is claimed. Unknown costs remain unapproved.') are opaque boilerplate that do not earn their place and push the useful scoping detail to the middle. The first sentence is front-loaded with the resource, which is good.

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?

There is no output schema and no meaningful annotation coverage of the return shape, yet the description never explains what a targetSpamScore is, its scale, or the response format. For a bulk lookup tool with an undocumented nested parameter object, this leaves an agent under-informed about both input shape and 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%, so the description must carry the load; it does partially by tying the tool to 'domain and page' targets, which maps to the kind enum. It never mentions the batch limit (max 20), the target string format, or that a single JSON array parameter carries both fields, so it only partly compensates.

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?

It names the resource (targetSpamScore values for domain and page targets from the Nexscope backlink index) but uses no clear verb and buries intent in jargon like 'Bounded domain and page targetSpamScore values'. An agent can infer it returns spam scores, but nothing distinguishes it from the many sibling backlink tools beyond an oblique reference to 'backlink overview'.

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 phrase 'Independently callable bulk interface sharing source facts with backlink overview' gestures at a relationship with a sibling but never states when to call this tool instead of the overview or other backlink tools. 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.