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

The description adds useful behavioral context about billing, confirmation, proxy limits, no automatic retries, and untrusted returned content. But it labels the operation 'BILLABLE READ' while annotations declare readOnlyHint=false and destructiveHint=true, which is a direct contradiction under the rubric.

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?

Front-loads the billable warning, then states purpose and constraints in dense, purposeful sentences. There is no filler and the length is appropriate for a billable external render 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?

Covers the key safety context: billing, required confirmation, proxy limitations, retry behavior, and untrusted output. It remains incomplete because block flags and waitForSelector are unexplained, and sibling differentiation is absent.

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 coverage is 57%; geo, url, confirm, and postWaitTime are documented, while blockMedia, blockImages, and waitForSelector are not. The description clarifies confirm and proxy restrictions but does not compensate for the undocumented parameters.

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?

States a specific verb ('Render') and resource ('one public page') and says it returns HTML. It does not name the sibling scrapeninja_scrape_page or explain how this differs from plain scraping.

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?

Provides constraints such as confirm:true, billing risk, basic proxies, and no premium proxies/custom scripts/headers/cookies/forms. However, it never explicitly says when to use this instead of scrapeninja_scrape_page; the JavaScript-rendering use case is only implied.

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