pay_for_resource

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

With no annotations, the description effectively discloses key behaviors: non-custodial wallet usage, price cap enforcement, and task query parameter handling. However, it omits details on error handling, async behavior, or settlement receipt format.

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?

Concise three-sentence description with no fluff. Each sentence adds distinct value: purpose, payment constraints, and security detail. Front-loaded with the core action.

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 no output schema, the description adequately states returns (content + receipt). However, for a payment tool, more detail on failure modes or processing expectations would enhance completeness.

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 0%, so description must explain parameters. It clarifies max_price_usdc (price cap) and task (query param), but url is only implied by the tool's purpose. Defaults are mentioned but not fully explained.

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?

Clearly states the verb 'Pay for and fetch' and the resource 'a paywalled resource'. Differentiates from sibling tools (discover, list, history) by focusing on executing payment and fetching content.

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?

Implies usage when needing to retrieve a paywalled resource, but lacks explicit guidance on when not to use or alternatives. Does not mention prerequisites like having discovered payment rails or sufficient funds.

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