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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, so the safety profile is covered. The description adds real value beyond that: it states the results come from a bounded crawl sample, that ownership/version/expiry/membership are validated at run time, and that diagnostics are returned for missing fields — meaningful operational context an agent cannot get from the annotations.

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?

Three short sentences with no filler, and the scope limitation is placed early. The first clause is mild title repetition, but overall it is tight and front-loaded.

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?

There is no output schema, so the description carries the return-value burden; "typed source evidence and missing-field diagnostics" gestures at it but does not describe structure or shape. Combined with the unexplained task_id and the absence of any failure-mode note beyond the membership check, it is adequate but leaves real gaps for a two-required-param, open-world tool.

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 description says nothing about either parameter. In particular task_id is completely unexplained — the agent must guess that it is a crawl-sample identifier and where to obtain it. With no schema text to lean on, the description should have compensated and does not.

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 opening clause largely restates the title ("Page Structured Data from a bounded crawl sample"), but the second sentence adds that it returns typed source evidence and missing-field diagnostics. It never specifies what kind of structured data (schema.org/JSON-LD/Open Graph) or what the evidence looks like, so the agent gets a rough direction but no precise resource definition.

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?

"This sample does not describe every page of a website" is a genuine usage caveat that warns the agent about coverage limits. However, there is no positive guidance on when to pick this tool, and no reference to closely related siblings such as nexscope_page_evidence or nexscope_seo_page_evidence, leaving routing to inference.

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