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

Beyond the annotations, it discloses that results are bounded, non-paginated, require cost approval before execution, and that 'proprietary rankings are not Google ratings or measured traffic' – real behavioral context an agent would otherwise get wrong. Annotations give readOnlyHint=false and openWorldHint=true, consistent with a credit-consuming external call, so nothing is contradicted.

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?

Five short sentences with the purpose front-loaded and no filler, but several sentences are terse to the point of being cryptic ('Preserve target kind and provider scope'), spending words without conveying meaning.

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?

A nested-object tool with 0% schema description coverage and no output schema needs the description to explain parameter shapes and what comes back; it explains neither. The caveats about rankings and cost are useful but do not fill the parameter gap.

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 parameters are nested, yet the description only offers 'Preserve target kind and provider scope', which does not explain DOMAIN vs PAGE semantics, the expected target string format, or what limit controls. It leaves the only guidance for the required nested object effectively uninterpretable.

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 resource and source: 'referring domains projection from the Nexscope backlink index', which an agent can map to the tool name. It does not distinguish itself from close siblings such as nexscope_seo_referring_networks or nexscope_seo_backlink_records, so an agent must infer the boundary.

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 gives operational constraints ('No pagination or additional provider calls', 'Unapproved costs prevent execution') but never says when to choose this over the related backlink/referring-networks tools. There is no explicit when-to-use or when-not-to-use guidance.

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