create_withdraw_link

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

With no annotations, the description carries full burden. It discloses that the tool opens a browser for QR scanning, requires an operator key, and that omitting amount_sats sweeps the balance. However, it doesn't specify return values or potential side effects beyond creation.

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?

Three sentences, each conveying essential information: purpose, behavioral aspect, and parameter usage with requirement. No unnecessary words.

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 effectively covers purpose, key usage, and a prerequisite. It lacks details on return value or errors, but for a single-parameter tool, it is fairly complete.

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% (one parameter described in schema). The description adds behavioral context: 'Omit amount_sats to sweep full balance' and the overall purpose, going beyond the schema's description.

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 verb (Create) and the resource (LNURL-withdraw link for operator to receive funds). It distinguishes from siblings like 'claim_lnurl_withdraw' and 'withdraw' by specifying it's for creation.

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 parameter usage guidance ('Omit amount_sats to sweep full balance') and a prerequisite ('REQUIRES OPERATOR KEY'), but does not explicitly state when to use this tool versus alternatives like 'claim_lnurl_withdraw' or 'withdraw'.

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