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

Annotations already flag the operation as read-only, idempotent, and non-destructive, so the description only needs to add behavioral context; it does so by revealing the execution mechanism (headless browser + proxy rotation) and supported behaviors (JS rendering, geolocation, ad-blocking). It could add credit-cost or failure caveats, but the key behavior is disclosed without contradicting the annotations.

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 dense sentences plus one example, with the core purpose front-loaded and no filler. The example earns its place by showing the expected call shape, and the whole description remains short enough to scan.

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?

For an 8-parameter, no-output-schema tool, the description covers the essential return type (HTML) and the major behaviors, while the schema covers every parameter. It is slightly incomplete around cost or rate-limit implications of premium_proxy/stealth_proxy, but an agent can call it successfully for the common case.

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 carries the parameter meaning; the description's inline example reinforces url/_apiKey/render_js but adds no semantics not already in the schema. A baseline 3 is appropriate because the description makes the primary parameters easy to spot without needing to compensate for schema gaps.

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 begins with a specific verb+resource pair: 'Fetch and render any web page through ScrapingBee', and states the exact output ('returning the resulting HTML'). This makes it clear this is the generic HTML-fetch tool rather than the structured extraction or search-focused siblings, even without naming them.

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 capability context ('Handles JS-heavy sites, geolocation, and ad-blocking') and a concrete invocation example, so an agent can infer common use cases. However, it never explains when to prefer this over scrapingbee_ai_extract or scrapingbee_google, nor lists any exclusions or when-not-to-use conditions.

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