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

With no annotations, the description carries the full burden and does so richly: it discloses atomicity (wallet checked for amount plus routing fee, payment claimed in DB before sats leave), idempotency (retries/double presses collide on a primary key; re-calling after success reports the existing payment), and irreversibility. These are exactly the behavioral traits an agent needs for a real-money mutation.

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?

Front-loads the operator instruction and the core action, then layers atomicity and idempotency detail. Dense and mostly waste-free, though it runs several sentences and could tighten the ledger-integrity exposition.

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?

An output schema exists so return values need no explanation, and the description fully covers auth (operator proven), mutation semantics, idempotency, and irreversibility. Nothing an agent needs to invoke this correctly is missing.

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 75%, so most parameters are documented in the schema itself. The description adds meaning to match_id and kind indirectly (amount is read from the settlement, the charity leg pays the recorded beneficiary), but it never explains npub or dpop_token usage beyond the schema. Baseline 3 is appropriate.

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 (send a settled match's charity or winner share over Lightning) with scope (operator-only). It actively distinguishes itself from siblings like beesknees_pay_charity and beesknees_payout by declaring it is the only tool that moves real sats and cannot be undone by writing another row.

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?

Frames the caller as the operator and clarifies that nothing is automatic, giving clear context for when it should fire. It does not explicitly name a sibling alternative or state a when-not condition beyond the restricted-operator gate, so it stops short of full routing guidance.

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