pay_lnurl

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

No annotations are provided, so the description bears the full behavioral burden. It implies an irreversible transfer of funds but says nothing about fee handling, required wallet balance, permissions, whether a fee estimate should precede it, or what is returned on success/failure.

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 single sentence is front-loaded and waste-free, but conciseness here reflects under-specification rather than discipline; a funds-moving tool warrants more structure.

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 destructive payment operation with no annotations and no output schema, the description omits nearly everything an agent needs: fee behavior, failure modes, and what a successful response indicates.

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 all three parameters (wallet_id, lnurl, amount) are already documented in the schema. The description adds only the parenthetical gloss on LNURL, which is baseline-level value.

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?

States a specific verb ('Pay') and resource ('LNURL (Lightning URL)'), and glosses the acronym so an agent knows this is a Lightning payment. It does not differentiate LNURL from the many sibling payment tools (pay_invoice, pay_lightning_address, l402_pay), so it stops short of a 5.

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?

There is no indication of when to choose this over pay_invoice, pay_invoice_with_amount, pay_lightning_address or l402_pay, and no preconditions are stated. The agent must infer the choice purely from the tool name.

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