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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions auto JS rendering, robots.txt compliance, pricing tiers, and caching behavior (half price for cached results). These go beyond a basic summary and provide useful operational context, though it lacks details on error handling or rate limits.

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 a single, well-structured sentence that front-loads the core purpose ('Extract a web page to clean Markdown + metadata') and appends key behavioral and pricing details without unnecessary words. 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?

Given the absence of an output schema and annotations, the description reasonably covers the essential aspects: what it does, return type (Markdown + metadata), behavioral constraints (robots.txt, JS rendering), and payment information. It does not address error conditions or authentication details, but for a relatively simple extraction tool, the information provided is fairly complete.

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 schema only describes x_payment, leaving url and mode without descriptions. The description adds context by explaining the pricing difference between fast and rendered modes, which hints at the mode parameter's semantics, but it does not explicitly define each enum value or the URL format. The low schema coverage is only partially compensated.

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 clearly states the tool's function: 'Extract a web page to clean Markdown + metadata' with a specific verb and resource. It also adds distinguishing behavioral context (auto JS rendering, robots.txt respected) that sets it apart from document parsing siblings like parse_document or structured_extract.

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 implies use for web page extraction, but provides no explicit guidance on when to use this tool over alternatives such as parse_document, structured_extract, or ocr_image. There are no mentions of exclusions or specific scenarios where this tool is preferred.

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