web_extract

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

No annotations provided, so description carries full burden. Discloses provider behavior (auto fallback) and options like include_images and render_js, but does not mention safety (read-only), rate limits, authentication, or error handling.

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 concise sentences with front-loaded key information: purpose, supported providers, and auto mode behavior. Every sentence 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?

No output schema exists, so description must describe return values. It only mentions formats (markdown/html) but not the structure (e.g., string, JSON with metadata). Also lacks details on URL limits, error handling, or effect of boolean parameters on output.

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 coverage is low (17%). Description adds value by naming providers and explaining auto mode, and mentions formats. However, it does not explain include_images, include_raw_html, or render_js beyond their names, leaving 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?

Description explicitly states the tool extracts markdown or HTML from URLs, lists supported providers, and explains auto mode fallback. The verb 'extract' and resource 'URLs' clearly distinguish it from sibling 'web_search' which likely searches for URLs.

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?

Provides detailed guidance on provider selection and auto mode fallback order. However, no explicit statement on when to use this tool vs web_search, nor any exclusions or alternatives.

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