await_settlement

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

Describes polling interval (every 5s), timeout (max 600s), and handling of timeout expiry. Lacks mention of error states or invalid IDs, but main behavior is transparent. No annotations provided, so description carries full burden.

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 and well-structured: purpose sentence, behavioral paragraph, guidance sentence, then argument descriptions. No redundant or missing information.

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?

Comprehensive for a polling tool: covers behavior, parameters, usage context, and timeout handling. Output schema exists, so return values need not be explained.

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?

Adds significant meaning beyond the schema: explains `payment_request_id` as returned by `create_payment_request` and provides range and default for `timeout_seconds`. Schema itself has no property descriptions (0% coverage).

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 awaits settlement of a payment request via polling. Distinguishes from siblings like `check_payment` which likely only checks status without waiting.

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 explicit guidance: 'Call this after sending the QR to the payer' and advises on timeout behavior. Does not explicitly exclude use cases but context is sufficient.

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