test-payment

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

Description explains the process involves a handshake, verification of wallet, signing, and settlement. It mentions free vs. paid products, indicating different behaviors. Without annotations, it covers key behaviors but omits details like side effects or errors.

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 sentences with no wasted words. First sentence states purpose, second gives recommended usage, third allows customization. Highly efficient.

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 and no output schema, the description adequately covers what the tool does and how to use it. Minor gap in explaining output or failure modes, but overall sufficient.

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 100% with a single optional parameter. Description adds meaning by providing a default URL and example, going beyond the schema's description.

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 it walks through a test-payment handshake, verifying wallet, signing, and settlement. It specifies a concrete first stop and differentiates from siblings by focusing on testing end-to-end, unlike 'how-do-i-pay' or 'verify-my-purchase' which have different purposes.

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?

Suggests a first stop (Underground Cultural District) and allows custom merchant URL, providing context for when to use. However, it does not explicitly state when not to use or compare with sibling tools, though the context is implied.

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