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

Annotations already declare readOnly, openWorld and non-destructive, so the safety profile is covered. The description usefully adds that results come from a bounded sample and that source ownership/version/expiry/membership are validated at run time, but these phrases are cryptic and don't say what the agent should do with them.

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?

Four short sentences, front-loaded with the scope constraint, no filler. Slightly redundant phrasing ('website page checks … every page of a website') but generally efficient.

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?

No output schema and 0% parameter documentation means the description carries the full burden, yet it never explains how to obtain the required task_id or what the returned evidence/diagnostics look like. For a read tool needing a task handle, this is a significant 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%, yet the description says nothing about `task_id` (required — where does a crawl task ID come from?) or `limit` (max 10). With two undocumented parameters and no compensating text, an agent lacks the meaning needed to call it correctly.

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 states the resource ('Website Page Checks') and hints at output ('typed source evidence and missing-field diagnostics'), but 'checks' is not a concrete operation and it does not differentiate from close siblings like nexscope_website_audit_summary or nexscope_seo_page_evidence. An agent can't tell precisely what this does or how it differs.

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 notes the bounded-crawl-sample limitation but gives no when-to-use guidance, no prerequisites, and no named alternatives among the many website_*/page_* siblings. The selection decision is left entirely to inference.

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