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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: per-feature credit costs and the option to attach a screenshot. However, it says nothing about the many behavioral knobs (wait, wait_for, wait_browser, timeout, block_ads, block_resources, cookies, capture_runtime_issues).

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?

Compact and front-loaded: core behavior first, then costs, then the screenshot option, with zero filler sentences. It is dense rather than bloated, though the cost list is somewhat shorthand for a reader unfamiliar with the tiering.

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 a 14-parameter, open-world scraper with no output schema, the description omits most of the configurable behavior an agent needs to call it well. It covers the headline output and pricing but not enough of the request semantics to be self-sufficient.

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 only 7% across 14 parameters, so the description must carry the load and largely does not. It explains format, render_js, screenshot, premium_proxy and stealth_proxy, but leaves roughly nine parameters (wait, wait_for, wait_browser, timeout, cookies, block_ads, block_resources, capture_runtime_issues) undocumented anywhere.

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 and resource (fetch a public web page, return content as markdown) with a precise output format. It doesn't name or contrast any sibling such as extractStructuredData or runBrowserScenario, so the agent gets a clear action but no routing signal.

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?

No explicit when-to-use or when-not-to-use statement and no named alternative among the 22 siblings. The credit tiers (render_js 5, premium_proxy 10, stealth_proxy 75) implicitly hint at escalating cost and therefore when each option is warranted, which is useful but indirect.

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