url.render

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

The description discloses key behaviors: headless browser, JS execution, and the available output formats. However, it does not mention error handling, rate limits, or other potential side effects. Since no annotations are provided, the description carries the full burden but is mostly sufficient.

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: two sentences that front-load the purpose. Every sentence adds value with no wasted 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?

Given no output schema, the description should clarify the output structure. It implies the output format matches the format parameter (markdown, text, etc.) but does not describe the return structure. Additionally, it omits explanations for timeout and waitUntil parameters. It is adequate but not fully complete.

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?

With 0% schema description coverage, the description should explain all parameters. It only mentions the 'format' parameter by listing the enum options. The 'url', 'timeoutMs', and 'waitUntil' parameters are not explained, leaving the agent without additional context beyond the schema's property definitions.

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 that the tool renders a page in a headless browser with JS execution for client-rendered/SPA pages. It specifies the resource (URL rendering) and the verb (render), and distinguishes itself from url.clean.

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 tells when to use this tool (for client-rendered/SPA pages) and when not to (use url.clean for server-rendered pages). It also notes the cost tier (~10× url.clean), providing clear guidance.

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