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

Annotations already declare read-only, non-destructive, open-world behavior, and the description goes beyond them with genuinely useful traits: results are proprietary rankings, not Google ratings or measured traffic; results are capped (no pagination); and execution is gated on cost approval. These caveats materially change how an agent should interpret and present the output.

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 no filler, and the core statement of what the tool does is front-loaded. The telegraphic phrasing ("Preserve target kind and provider scope") costs some readability but nothing is padded.

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 two-parameter read-only tool with no output schema, the description covers data provenance and cost gating but omits what the returned page records look like and how the target string should be formed. It is adequate on caveats, thin on operability.

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 explain the two parameters and it largely does not: "target" is never defined (domain vs URL vs kind) beyond the cryptic "Preserve target kind", and the interaction between "limit" and the stated "no pagination" is left implicit. Only a fragment of meaning is added over the bare schema.

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 pages projection from the Nexscope backlink index" identifies the resource area (pages on a domain in a backlink index) but uses jargon ("projection") instead of a concrete verb like "list pages" and never differentiates from close siblings such as nexscope_seo_top_pages or nexscope_seo_backlink_records. An agent can guess the domain of the tool but not precisely what it returns.

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 states constraints ("No pagination or additional provider calls", "Unapproved costs prevent execution") but never says when to choose this tool over the many backlink/top-pages siblings. No alternatives or exclusion conditions are named, so selection guidance is absent.

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