Read a web page as Markdown

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

Annotations already declare readOnlyHint and openWorldHint. The description adds real behavioral context beyond that: it strips navigation/adverts/scripts, and it explains the JS-rendering path. It stops short of noting caching behavior or rate limits, but covers the important traits.

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?

Two sentences, zero filler, with the core purpose and output format front-loaded and the conditional tip second. Every clause earns its place.

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, and it does state the output is Markdown main content with truncation signaled. For a read-only 7-param tool with full schema coverage, this is essentially complete, though it could confirm the public-only/no-auth boundary.

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 coverage is 100%, so the 3 baseline applies, and the description earns above it by tying the render parameter to a concrete condition (JavaScript-built content). The other six parameters are left entirely to the schema, which is adequate but not additive.

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 (fetches) and resource (public web page) plus the output format (main content as Markdown with navigation, adverts and scripts stripped). It is clearly distinct from siblings like read_qr_code or capture_screenshot, though it does not name any sibling directly for differentiation.

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 only explicit guidance is conditional on the render flag (JS-built pages). There is no statement of when to prefer this over render_html, preview_link or convert_html_to_markdown, so usage is only implied by the 'public web page' framing.

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