pay_with_nwc

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

No annotations exist, so the description carries the full behavioral burden. It does not disclose that paying is irreversible, that it spends funds, that amountless invoices require amountMsat, or how the nwcUri fallback to an environment variable behaves. The single sentence covers mechanism but not operational consequences.

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 a single focused sentence and is easy to parse. The parenthetical 'alias' saves space but adds ambiguity, preventing a perfect score.

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?

For a payment operation with no annotations and no output schema, the description is too thin. It omits usage selection, behavioral warnings, and any clarification of the alias relationship, leaving an agent under-informed about a financially meaningful call.

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 description coverage is 100%, so the parameters are already fully documented. The description adds only the 'BOLT-11' context for the invoice, which is marginal value 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?

The description states a specific action ('Pay'), a specific resource ('BOLT-11 Lightning invoice'), and the transport method ('NIP-47 Nostr Wallet Connect'). It is clear on its face, though it does not explicitly differentiate itself from the sibling 'pay_lightning_nwc' beyond the parenthetical 'alias.'

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 guidance is given about when to use this tool versus alternatives such as 'pay_lightning_nwc' or 'pay_cashu_nutzap'. The word 'alias' hints at a relationship to another tool, but the description never says whether this is the same operation, a fallback, or a preferred path.

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