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

Annotations already establish readOnly, idempotent, non-destructive, and open-world behavior. The description adds useful context beyond annotations: it emphasizes the page must be public (auth expectations), the result is a compact text representation, and sessions/selectors are unsupported. It does not mention rate limits or failure modes, but for a read-only fetch that is a minor gap.

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 a single dense sentence that front-loads the core action and result, then enumerates outputs and exclusions efficiently. There is no filler or redundant restating of the tool name.

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 only partial parameter documentation, the description gives a good high-level view of return content but leaves parameter semantics underspecified. An agent could invoke with defaults, but understanding how delayMs, viewport, or maxTextChars affect behavior would require guessing.

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 only 25%, with url being the only described parameter. delayMs, viewport, and maxTextChars have types/defaults but no semantic explanation, and the description does not compensate by explaining these parameters or how they affect the rendered output.

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 clearly states the verb ('Render'), the resource ('a public web page'), and the concrete output ('visible text, clean Markdown, headings, links, forms, basic image metadata and interactive elements with bounding boxes'). It also differentiates itself from visual/crawling tools by explicitly excluding OCR, visual inference, crawl, sessions, and advanced action selectors.

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 conveys it is for text-only agent consumption and lists what it does not do, giving clear context on appropriate use. However, it never names the sibling tool capture_website or explicitly says 'use this instead when you need X', so it stops short of full when/when-not alternative guidance.

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