Fetch Page

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only mentions the proxy but does not explain response format, redirect handling, error behavior, or authentication requirements. The clarity that it fetches 'public' pages is minimal and does not set expectations for the agent.

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 a single, concise sentence with no unnecessary words. It is front-loaded with the core action and proxy context, making it efficient. However, it could be expanded with behavioral details without sacrificing conciseness.

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 absence of annotations, output schema, and parameter descriptions, the tool description is insufficiently complete. It does not provide enough context for an AI to understand return values, parameter effects, or how it differs from 'check_exit_ip' in practical scenarios.

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?

The input schema has 5 parameters with 0% description coverage, and the description does not mention any parameter meaning or usage. It fails to clarify the purpose of 'raw', 'city', 'country', or 'session', leaving the agent without any semantic guidance beyond variable names.

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 public HTTP(S) page through a DataImpulse residential proxy, using the specific verb 'Fetch' and a well-defined resource. It distinguishes itself from the sibling tool 'check_exit_ip' by focusing on page retrieval rather than IP inspection.

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 provides no guidance on when to use this tool versus the sibling 'check_exit_ip' or any alternatives. It lacks contextual cues such as 'use this when you need to retrieve web content' or exclusions like 'not for authenticated pages'.

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