payment_quote

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

With no annotations, description carries full burden. It clearly states the tool does not pay (non-destructive) and that spending policy is operator-owned and not widen-able. Adds crucial behavioral context beyond schema.

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: first states core action with important disclaimer (WITHOUT paying), second enumerates return data, third adds policy context. Front-loaded, no fluff.

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?

Description adequately covers main purpose and return data but lacks details on parameters, error handling, and output format. No output schema provided, so description is helpful but not complete for all 6 parameters.

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 compensate. It only implicitly explains 'url' via context; parameters body, chain, method, headers, tokenAddress are not described. Description adds minimal value for parameter meaning.

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?

Description clearly states the tool checks cost and policy allowance for a paid URL without actually paying. It specifies verb (check), resource (paid URL cost, policy decision), and distinguishes from siblings like paid_fetch (actual fetch) and spend_status (status).

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?

Description implies usage for pre-payment checks but does not explicitly state when to use over siblings or provide exclusions. No mention of alternatives or when not to use.

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