Read a web page

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly adds important behavioral traits: automatic anti-bot handling, billing per successful page, and that failures are free. This gives the agent useful context beyond the basic fetch operation, though it does not mention redirects or rate 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 two sentences, front-loaded with the primary action and resource. Both sentences earn their place: the first explains what the tool does and output options; the second explains billing behavior. No fluff or 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?

For a simple one-URL fetch tool with two parameters and no output schema, the description covers the main aspects: purpose, output formats, anti-bot handling, and pricing. It is complete enough for an agent to understand the tool's basic scope, though it lacks details on potential failure modes (beyond 'free') or limits, which is acceptable for this simplicity.

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 100%, so the schema already documents both parameters (url and format). The description adds no additional parameter-specific details; it only mentions output formats generally, which is already covered by the enum. Baseline 3 is appropriate.

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 uses a specific verb 'Fetch' with a precise resource 'any URL' and clearly states the output format ('clean, LLM-ready markdown (or html/text)'). It distinguishes itself from sibling tools like crawl_site by focusing on fetching a single page rather than crawling.

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 usage for fetching a single URL as markdown, but it does not explicitly state when to use this tool over alternatives (e.g., crawl_site for crawling multiple pages) or when not to use it. The guidance is present but implicit.

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