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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds meaningful behavior beyond that: results come from a bounded crawl sample, include typed source evidence and missing-field diagnostics, check ownership/version/expiry/membership, and do not describe every page of the site.

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?

The description is short and front-loads the core idea, followed by useful caveats about sample scope and checks. It avoids repetition, though the phrase 'when run' is slightly awkward and a little more precision would not hurt.

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?

With no output schema and 0% parameter description coverage, the description needs to carry much more of the operational burden. It explains sample scope but leaves critical gaps around the required task_id, pagination parameters, pageUrl filtering, and what the returned evidence actually contains.

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?

The schema has four parameters with 0% description coverage, including the required task_id plus limit, offset, and pageUrl. The description does not explain any parameter name, meaning, or expected value; 'bounded crawl sample' does not clarify how task_id or pagination work.

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 says it reports 'Website Resource Status from a bounded crawl sample' and returns 'typed source evidence and missing-field diagnostics.' However, it never defines what 'resource status' means or what class of resources are covered, so an agent cannot clearly distinguish it from nearby website/page audit siblings without guessing.

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?

It offers no explicit guidance on when to use this tool versus alternatives such as nexscope_website_page_checks, nexscope_website_links, or nexscope_website_audit_summary. The only usage-like statement is that checks happen 'when run,' which is not a selection rule.

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