web_search_and_fetch

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does disclose that rendered=True drives a headless browser and requires RENDER_ENABLED=true, and that it fetches from each result URL. However, it omits potential issues like rate limits, latency, fetch failures, or how many URLs are actually processed.

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 the core operation front-loaded and the conditional rendered caveat placed after. Every sentence earns its place and there is no redundancy.

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?

The output schema covers return shape, so that omission is acceptable. However, for a compound tool with no annotations, the description leaves meaningful gaps around max_results behavior, fetch error handling, and operational implications of fetching multiple URLs.

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 0%, and the description only explains the rendered parameter. The query and max_results parameters receive no semantic explanation beyond their names, and max_results in particular is non-obvious regarding how it limits the fetch stage.

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 states a specific compound action: search the web, then fetch and extract text from each result URL. This clearly distinguishes it from the sibling tools web_search and web_fetch, which each cover only one stage of the workflow.

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 this tool is for combined search-and-fetch workflows, but it never explicitly names the sibling tools or states when to prefer a single-stage tool instead. The usage guidance is left mostly to inference.

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