pay-offer

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It only states 'Pay a bolt12 offer' without revealing side effects (e.g., irreversible sending of funds), authorization requirements, or error conditions. Critical information for a payment action is missing.

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?

The description is extremely concise at one sentence, which is efficient. However, it lacks any additional structure or explanation (e.g., what a bolt12 offer is). While not verbose, it sacrifices completeness for brevity.

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 and no annotations, the description should provide more context about what happens when the tool is used (e.g., confirmation, result). For a payment tool that moves funds, the description is insufficiently complete. The agent is left without behavioral or return value information.

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 all parameters adequately described in the input schema. The description itself adds no further parameter-level semantics. Baseline score of 3 is appropriate as the schema already documents the parameters.

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?

The description clearly states the action ('Pay') and resource ('bolt12 offer'). While it doesn't explicitly differentiate from siblings like pay-invoice, the tool name itself distinguishes it (bolt12 vs bolt11). The description is sufficient for an agent to recognize the core purpose.

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?

No usage guidance is provided. The description does not mention when to use this tool over alternatives (e.g., pay-invoice for bolt11, pay-lightning-address for LNURL) or any prerequisites. An agent receives no help in deciding between this and sibling payment tools.

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