paid_fetch

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

No annotations present, so description carries full burden. It discloses automatic payment behavior, operator threshold checks, and that free URLs cost nothing. Does not cover failure behavior or rate limits, but adequately covers key behaviors.

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, front-loaded sentences with no fluff. Each sentence adds essential information about function, usage guidance, and policy implications.

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?

No output schema exists, yet description does not mention return values. With 9 parameters, the description only covers payment-related semantics. Adequate for core behavior but missing parameter details and output format.

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 coverage is only 11% (only maxAmountUsd has a description). The description adds little parameter-specific meaning beyond the payment concept. Fails to explain url, method, headers, body, chain, dryRun, responseMode, tokenAddress.

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 URL and automatically pays if required, distinguishing it from siblings like payment_quote. It uses specific verbs and resources ('fetch a URL', 'paying if required').

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?

Provides clear context: mentions when to use payment_quote first as an alternative, and explains the spending policy and approval threshold. Lacks explicit exclusions for other sibling tools, but gives solid guidance.

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