gate_fetch

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

The description discloses key behaviors: automatic payment, payment priority (prepaid then escrow), refusal on cap exceed, and no cost for ungated URLs. Since no annotations are provided, the description adequately carries the transparency burden, though it could mention that it deducts from the wallet balance.

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?

Three concise sentences with no fluff. The main action is front-loaded, making it easy to understand quickly.

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 one parameter, no output schema, and no nested objects, the description provides sufficient information about purpose, usage, and behavior. It mentions return value (content and payment info).

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?

Only one parameter 'url' with 100% schema coverage. The parameter description adds value by explaining the automatic payment on HTTP 402 and advising to check price first when cost matters.

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 Gate-protected URL and automatically pays the paywall. It is distinct from sibling tools like gate_get_price and gate_prepaid_balance.

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 explains that the tool automatically pays from the wallet, prefers prepaid, uses escrow otherwise, and refuses if caps exceeded. It also mentions ungated URLs are free. It suggests checking price first with gate_get_price, but does not explicitly state when not to use it.

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