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

With no annotations present, the description carries the full burden and does a solid job: it discloses the browser/QR side effect, the routing-reserve-driven 10 sat floor, the absence of a platform fee, and the operator-key authorization requirement. It stops short of saying whether the link expires, is single-use, or how the link is returned.

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?

Four short sentences, zero filler, with the core purpose front-loaded and the hard precondition ('REQUIRES OPERATOR KEY') isolated in caps at the end so it is not buried mid-sentence.

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 single-optional-parameter tool with no output schema, an agent has enough to call it correctly: what it produces, the amount semantics, and the auth gate. The main gap is what the caller actually gets back (a URL string? a QR image?) and link lifetime, which matters for a fund-moving operation.

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% and already documents amount_sats and the omit-to-sweep behavior, so the baseline is 3. The description adds genuine meaning beyond the schema by explaining the 10 sat minimum is measured after the routing reserve, which an agent could not infer from 'minimum: 10' alone.

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 and resource (create an LNURL-withdraw link) and clarifies the direction of funds — operator receives. It is distinguishable from claim_lnurl_withdraw by the 'create' vs 'claim' framing, but it never explicitly contrasts with the sibling withdraw tool, which also moves funds out.

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?

Usage is only implied by 'operator to receive funds' and the sweep option; the description never says when to pick this over withdraw, claim_lnurl_withdraw, or sweep_agent, all of which appear in the sibling list and touch the same balance.

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