url.render

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

The description discloses that the tool executes JavaScript in a headless browser, which is a key behavioral trait not derivable from the schema or annotations (which are absent). It also mentions the output formats are the same as url.clean and notes the cost multiplier. However, it does not discuss rate limits, error handling, or whether the tool is read-only, though the 'render' action implies read-only behavior.

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 two sentences long and front-loads the key distinction (headless browser > url.clean). It is efficient and contains no wasted words. A slight improvement could be adding a structured breakdown of parameters, but overall it is concise and easy to parse.

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 the absence of annotations and output schema, the description covers the core purpose, usage context, and key behavioral aspects (JS rendering, cost). The input schema provides enums and defaults, so the lack of parameter elaboration is partially compensated. However, for a tool with 4 parameters and no schema descriptions, the description could be more complete by detailing the optional parameters.

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 must explain parameters. It mentions 'Same formats (markdown/text/both/html/pdf),' which covers the format parameter but does not elaborate on the enum meanings. The waitUntil and timeoutMs parameters are not mentioned at all, leaving the agent without guidance on their purpose or defaults. The url parameter is obvious from the usage description but not explicitly detailed.

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 url.render is like url.clean but uses a headless browser for JavaScript execution, targeting client-rendered/SPA pages. It distinguishes itself from the sibling tool url.clean by specifying the type of page it handles, so the agent can select the correct tool based on rendering needs.

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 instructs to 'Use url.clean for server-rendered pages,' which implies using this tool for client-rendered pages. It also notes that it is Tier 2 (10x cost) compared to url.clean, providing practical guidance on cost implications and when to choose which tool.

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