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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them: rendering is browser-accurate, failures to load are surfaced in the output, and private spaces render under the caller's identity. It stops short of describing how failures are reported or what a partial render looks like.

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?

A single front-loaded clause that packs the resource, fidelity model, the two main variations and the failure-reporting behavior with zero filler. Nothing could be cut without losing information.

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?

Seven parameters with a conditional anyOf requirement (space or space_id) and an output schema covering the return value; the description need not restate defaults or response shape. The main residual gap is the lack of any routing hint against closely named siblings, which matters for a toolset this large.

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 every parameter carries its own inline description, including defaults (1280 width, 800 height, full_page default). The description only echoes the width and single-block capabilities, adding no format or interaction detail beyond the schema. 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+resource: a PNG of a published space rendered as a browser would draw it, optionally at a width or of a single block. That is clearly more specific than the name alone. It does not, however, differentiate from the sibling 'screenshot', which an agent must disambiguate on its own.

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?

There is no explicit when-to-use guidance and no named alternative. The description never says why an agent should pick this over the sibling 'screenshot', 'download_pdf', or 'export_space'. The mention of 'at any width or of one block' hints at responsive/block-level use cases but leaves selection to inference.

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