render

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

No annotations provided, so description carries full burden. It discloses cost, wallet requirement, headless browser with JS execution, markdown extraction, and a security note. It does not cover potential error behaviors or timeouts, but major behaviors are transparent.

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 extremely concise with two sentences, front-loading cost and wallet requirement, then the action, use case, and security note. No unnecessary words.

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?

For a single-parameter tool with no output schema, the description is fairly complete: it explains what the tool does, when to use it, and a security concern. It lacks details on return format (though markdown is mentioned) and error handling.

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%, baseline 3. The description adds context (cost, wallet) but does not add specific semantics to the url parameter beyond what the schema already states ('Public http(s) URL').

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 tool renders a page in a real headless Chromium browser with JavaScript execution and extracts main content as markdown. It distinguishes from plain fetching by specifying use for SPAs and JS-heavy sites.

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 explicitly recommends this tool for SPAs and JS-heavy sites where plain fetching returns empty shells, providing clear context. It does not exhaustively list when not to use, but it gives a strong usage hint.

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