pay_payment_request

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

Discloses the main action (settle) and testing purpose, but does not describe side effects like irreversible changes, error responses, or permissions needed. With no annotations, more detail would be beneficial.

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?

Two sentences, no redundancy. Purpose and key constraints are efficiently front-loaded.

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?

Lacks details on return value, error conditions, prerequisites (e.g., payment request must exist and be pending), and overall behavior. For a mutation tool with no output schema or annotations, more context is needed.

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?

All parameters are documented in the schema with 100% coverage. The description mentions assetType and asset reference but adds no new semantic meaning beyond the schema.

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 tool settles a payment request, specifying it's sandbox-only and for testing webhook/settlement flows. Distinct from siblings like create_payment_request or void_payment_request.

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 context that tool is for testing webhook/settlement flows, implying when to use. However, no explicit when-not-to-use or comparison to alternatives like void_payment_request or create_refund.

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