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

Annotations already declare read-only/idempotent/non-destructive, but the description adds real behavioral context beyond them: returns a JSON artifact plus archived asset references, never executes or fetches source URLs, fails explicitly when the source document is missing, and the consumer must sandbox untrusted HTML/CSS/SVG. These are exactly the failure modes an agent needs to plan around.

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 purpose and scope in the first sentence, then constraints, return shape, failure mode, and safety handling in order. Dense but every clause carries content; it could be tightened slightly into shorter sentences but nothing is redundant.

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?

An output schema exists, so return values need not be detailed, yet the description still names the artifact shape and asset references, plus the missing-document failure path and untrusted-content handling. Nothing an agent needs to call this safely is absent.

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 100% and each parameter already carries detailed guidance (page key vs URL, exact view profile, pinning an exact version, environment omission rule). The description adds no parameter-level information, so the baseline 3 applies.

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?

States a specific verb (export) and precise resource (captured scriptless source document: hydrated HTML + original stylesheets), and explicitly separates it from what it is not — live browser access or the canonical scene. An agent can tell this apart from the many get_page_*/get_component_* siblings that return derived artifacts.

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?

Gives positive conditions (explicitly requested Web diagnostics, HTML baseline comparison) and a negative one (not live access, not a replacement canonical scene). It does not name a specific sibling alternative for the cases it excludes, so routing is implied rather than fully explicit.

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