fetch_web_content

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

No annotations are provided, so the description must cover behavioral traits. It mentions 'any public URL' and optional filtering, but omits details on error handling, redirects, authentication, or rate limits. The transparency is basic.

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 structured with a clear header, Args list, and Returns section. It is not overly long, though the prompt examples could be slightly trimmed. Overall, it is efficient.

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 description covers the basic inputs and output, but lacks details on error scenarios, maximum allowable characters, or non-HTTP content handling. With no annotations, more context would be beneficial for complete understanding.

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 0%, requiring the description to add meaning. It does so by describing the URL as 'public HTTP/HTTPS URL,' the prompt as an optional filter with examples, and max_chars with its default. This adds significant value beyond the schema.

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 'Fetch and extract text content from any public URL,' providing a specific verb and resource. It distinguishes from the sibling 'web_search' by focusing on fetching a known URL rather than searching 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?

The description explains the prompt parameter and default max_chars, implying usage for targeted extraction. However, it does not explicitly contrast with the sibling 'web_search' or state when not to use this tool, leaving room for ambiguity.

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