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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds valuable behavioral detail beyond those hints: it reveals that the tool executes JavaScript in headless Chromium and returns the post-execution HTML, which is material to an agent deciding whether this tool will satisfy its goal.

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 compact, front-loaded with the tool's core behavior, and includes a concrete invocation example in the second sentence. Every part earns its place, and there is no redundant restating of the tool name or title.

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 explains what the tool returns (fully-executed HTML after JavaScript runs), gives a clear use case, and provides a working example. Since there is no output schema, this return-value description is essential and is sufficiently complete for an agent to invoke the tool correctly.

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%, so the schema already documents all four parameters. The description adds only a usage example showing the url and _apiKey, which is helpful but not necessary for understanding parameter meaning. This matches the baseline for fully covered schemas.

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 specifies a clear verb and resource ('Render a URL in headless Chromium') and a concrete outcome ('fully-executed HTML after JavaScript runs'). It differentiates the tool's core behavior from a plain fetch, but it does not explicitly contrast with sibling tools like browserless_scrape or browserless_smart_scrape, so the differentiation from siblings is inferred rather than stated.

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 gives an explicit condition for use: 'use this when a plain fetch returns an empty shell or JS-rendered SPA.' This provides clear context for when to choose the tool, though it does not mention when not to use it or name alternative sibling tools such as browserless_scrape or browserless_screenshot.

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