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

No annotations are provided, so the description carries the full burden. It does disclose useful capabilities (anti-bot bypass, JS rendering, LLM-ready output), which is real behavioral value, but omits rate limits, auth requirements, timeout behavior, and failure modes for blocked pages.

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?

A single sentence that front-loads the differentiating capabilities with zero filler. Every clause earns its place.

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 two-parameter scraping tool with no output schema, the description covers capability and output format (Markdown) adequately. It falls short only on operational details like timeouts and error behavior for pages that resist scraping.

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 both target_url and wait_for_js are already documented in the schema. The description adds no syntax, format, or default information beyond what the schema provides, so baseline 3 applies.

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 specific verbs (bypass, render, extract) and a concrete resource (clean LLM-ready Markdown from any URL). This is the only scraping tool among a sibling set of data-lookup APIs, so the distinction is obvious without opening any schema.

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 explains what it does but gives no guidance on when to reach for it versus other tools, nor any exclusions or prerequisites. An agent must infer usage entirely from the name and capability list.

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