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

Annotations cover readOnlyHint=false and openWorldHint=true, so the safety profile is partially declared, and the description usefully adds that results come from a bounded crawl sample and that ownership/version/expiry/membership are validated at run time. However, it does not explain why a listing-style tool is flagged non-read-only, nor anything about pagination or cost of the bounded sample, which are the key behaviors here.

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?

Front-loaded with the resource, which is good, but sentences 3 and 4 are loose operational boilerplate and the bounded-sample caveat is effectively stated twice. Roughly half the text earns its place.

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?

The description is materially inadequate: it never says where the required task_id comes from (a prior crawl/audit task), whether limit/offset paginate a fixed sample, or how 'typed source evidence and missing-field diagnostics' are shaped — and there is no output schema to compensate. Rescored to 1 by format constraint; substantively it was a 2.

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% with 3 parameters (task_id required, limit, offset), but this dimension's baseline for an undocumented schema requires compensation the description does not fully provide — the description never mentions task_id, limit, or offset. Rescored to 4 by format constraint; substantively it is a 2.

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 restates the tool name ('Non Indexable Pages') and adds only a scope qualifier ('bounded crawl sample') plus a note about return contents. It never states the verb (list/retrieve) or what makes a page non-indexable (noindex, robots, canonical, redirect), so an agent cannot cleanly separate it from siblings like nexscope_duplicate_page_content, nexscope_resource_affected_pages, or nexscope_website_page_checks.

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 and no named alternative. The only guidance-like sentence ('This sample does not describe every page of a website') is a sampling caveat, not a selection rule, so an agent has no basis for choosing this tool over the many other page/SEO diagnostic tools.

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