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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description goes well beyond that by disclosing idempotency keying (user, slug, UUID), owner-only free result retrieval via a specific endpoint, persistence in owner call history, and a seven-day source-freshness rule that applies only to dependent requests. The 'missing values are not zero' warning is a genuinely useful semantic disclosure that prevents misreading absent data. It does not mention rate limits or confirm whether execution is synchronous or async, keeping it short of a 5.

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 compact but front-loads the least informative sentence, burying the practically useful retrieval and freshness details in the middle. The closing sentence about examples describing structure only is meta-commentary of low value to an agent deciding whether to call the tool.

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, the description must carry the return-value burden, and it only gestures at it via 'separate collection snapshots and missing reasons' without naming what evidence fields come back. The retrieval path and retention behavior are covered, but the shape of the evidence payload remains unspecified.

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?

There is a single required parameter with 100% schema description coverage, and the schema already specifies the public HTTP(S)-only constraints, so the schema carries the full parameter burden. The description adds nothing about the url argument, which is acceptable given the coverage but warrants only the baseline 3.

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 phrase, 'Bounded page evidence with separate collection snapshots and missing reasons', is a noun phrase built from internal jargon rather than a verb-plus-resource statement of what the tool does. An agent cannot tell from this whether the tool scrapes a page, returns cached SEO signals, or triggers an async job, nor how it differs from siblings such as nexscope_page_structured_data, nexscope_page_screenshot, or nexscope_seo_page_backlink_composition.

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 never states when to choose this tool or when not to. The only routing hint is for retrieval, 'nexscope_seo_call_result', which is a downstream step rather than an alternative for creating evidence. No prerequisites, exclusions, or comparison to the many page-level sibling tools are given.

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