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

With no annotations present, the description carries the full burden of disclosing behavior. It does reveal that the tool uses JS rendering and claims blocking resistance, plus a per-call price, but it omits response format, timeout behavior, rate limits, failure modes, and whether any side effects occur. This is thin coverage for an unannotated tool.

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 very short and front-loads the most useful differentiators before the price. It wastes no words, though it is so terse that it sacrifices usable guidance.

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 tool has no annotations, no output schema, and a single parameter with zero documentation, the description should compensate by explaining what is scraped, what the output looks like, and when it should be chosen over sibling tools. The current one-liner leaves these essential operational details implicit.

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?

The only parameter, 'url', has no schema description and the tool description adds nothing about it. An agent can guess that 'url' is the target page to scrape, but the description does not clarify accepted schemes, redirects, rendering waits, or expected input formats, leaving the parameter's semantics under-specified.

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 identifies the tool as a 'browser scraper' and adds the meaningful qualifiers 'unblockable' and 'JS-rendering', which distinguish it from a generic web scraper. It lacks an explicit verb and does not specify exactly what is returned, but the core purpose is clear.

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 qualifiers 'unblockable' and 'JS-rendering' imply the tool should be used for dynamic or anti-bot-protected pages, providing a soft usage cue. However, it does not explicitly state when to prefer this tool over siblings like web_scraper or render_screenshot, and gives no exclusions.

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