fetch_webpage

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 mentions 'returns a simplified markdown representation', which adds some context about output format. However, it fails to disclose critical traits such as error handling, rate limits, authentication needs, or whether it's a read-only operation, leaving significant gaps for a tool that interacts with external resources.

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 with a single sentence that front-loads the core action and outcome. There is no wasted language, making it efficient and easy to parse for an agent.

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 has an output schema, the description doesn't need to explain return values in detail. However, with no annotations and low schema coverage, it lacks completeness in behavioral aspects like safety or performance. The description is adequate for a simple fetch operation but misses key contextual details for reliable use.

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%, so the description must compensate. It implies the parameter is a URL for fetching, but doesn't add specific meaning beyond what the schema's property name 'target_url' suggests. The baseline is 3 because the description provides minimal context without detailing format constraints or examples.

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 verb 'fetches' and resource 'webpage', specifying what the tool does. It distinguishes from siblings like 'search_on_web' by focusing on fetching a specific URL rather than searching. However, it doesn't explicitly contrast with 'search_on_website', which might involve similar operations.

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?

No guidance is provided on when to use this tool versus alternatives like 'search_on_web' or 'search_on_website'. The description implies usage for fetching a specific URL, but it lacks explicit when-to-use or when-not-to-use instructions, leaving the agent to infer context.

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