fetch_page

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

With no annotations provided, the description takes on the burden of disclosing behavior. It explains that it uses Readability-style extraction and removes navigation/ads, which is helpful. However, it does not disclose the return format, failure modes (e.g., invalid URL, non-accessible pages), or any rate limiting.

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 core purpose, and the second sentence adds valuable detail about extraction behavior without unnecessary fluff.

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 fetch tool, the description covers the main behavior but leaves gaps. There is no output schema, so the agent is left unsure whether the response is plain text, structured, or includes metadata. It also does not mention pagination or handling of very long pages beyond the max_length parameter.

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% since both parameters (url and max_length) have clear schema descriptions. The description adds context about extraction semantics but does not go beyond the schema for parameter meaning or usage details.

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 and resource: 'Fetch and extract the full readable content from a single URL.' It clearly distinguishes itself from sibling search and research tools by focusing on a provided URL rather than discovery or aggregation.

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 a known single URL, but it does not explicitly state when to prefer this over alternatives like web_search or deep_search, nor does it mention any prerequisites or excluded scenarios.

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