Browser render

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

Annotations already declare readOnlyHint and openWorldHint, so the description does not need to restate safety. It adds useful behavioral context by explaining that the tool runs headless Chrome and returns extracted DOM text rather than, say, a screenshot or raw HTML. The 'Opt-in' note also conveys that this is an intentionally chosen, more invasive rendering step.

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 short sentences carry the core information with no filler. The first sentence front-loads the purpose and output, the second delivers the critical opt-in behavior. This is an appropriately sized description for a straightforward tool.

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?

The description is adequate for a high-level understanding but incomplete for safe invocation without guessing. With no output schema and three parameters, the agent would benefit from knowing that max_chars bounds the returned text and that rendering can time out. The opt-in flag helps, but the description still leaves important operational details implicit.

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?

The schema has 0% description coverage, so the description must compensate, but it only says 'Render JS page' and 'return DOM text.' It never explains that max_chars truncates the returned text or that timeout_seconds bounds the render wait. The url parameter is implied by 'page,' but max_chars and timeout_seconds are left entirely to the agent to infer from their names.

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 names a specific verb and resource—'Render JS page in headless Chrome'—and clearly states the output: 'return DOM text.' This distinguishes it from plain fetch tools like http_fetch that do not execute JavaScript. The 'Opt-in' note further signals that this is a deliberate alternative to standard fetching.

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 'Opt-in' marker gives clear guidance that this tool should be used deliberately, not as a default fetch mechanism. It implies that the agent should choose it when JavaScript rendering is required, but it does not explicitly name the alternative or state 'use http_fetch for non-JS pages.' Thus it is clear but lacks explicit exclusions.

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