web_extract

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

No annotations present. Description mentions fallback behavior in auto mode but does not disclose rate limits, authentication needs, error handling, or reliability of external providers.

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 front-load the core purpose. Every word is valuable with no repetition or filler.

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?

Moderately complete: explains providers and output format but lacks details on boolean parameters, expected return type (no output schema), and error behavior, leaving gaps for a 6-parameter tool.

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 explains provider enum and format values but does not add meaning to boolean parameters like include_images, include_raw_html, or render_js, which remain unexplained.

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 clearly states 'Extract markdown or HTML from URLs' with specific verb and resource. Lists supported providers, distinguishing from sibling tool 'web_search' which searches rather than extracts.

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 guidance on provider selection with 'Auto mode tries Tavily first...', but does not explicitly state when to use extraction vs search or mention alternatives beyond listing providers.

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