web_fetch

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

The description discloses that image links and hyperlinks are removed to save token context size, and that output is in clean markdown. Since no annotations are provided, the description carries the full burden; it is transparent about these key behaviors but could mention error handling or size 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 extremely concise: two sentences plus an Args block. Every sentence provides value, and the purpose is front-loaded. No wasted words.

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 tool's simplicity (one parameter, no nested objects) and the presence of an output schema, the description covers all necessary aspects: purpose, behavior, and parameter meaning. No gaps.

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?

With 0% schema description coverage, the description adds necessary meaning to the 'url' parameter: 'The web URL to fetch and convert.' This clarifies the purpose beyond the schema's title and type. Could include examples or constraints.

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 'Fetches a webpage's content and converts it to clean markdown'. This specific verb-resource combination distinguishes it from sibling tools like web_search (search) and file operations (local files).

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 when you need the content of a specific URL, but does not explicitly compare with alternatives like web_search or mention when not to use this tool. No exclusion criteria or context are provided.

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