bountyRelease

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

No annotations are provided, so the description must disclose behavioral traits. It only states that it pays a bounty, but does not mention that this is an irreversible financial transaction, requires admin keys (lnbitsAdminKey), or any side effects. The schema includes sensitive parameters but the description does not address them.

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, concise sentence with the HTTP method and endpoint, making it front-loaded and efficient. However, it is slightly cryptic with the dash separation, though it earns its place.

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 tool with 8 parameters, no annotations, and no output schema, this description is severely incomplete. It fails to explain the required parameters (bountyId, recipientPubkey, bountyAmount), the role of bridgeUrl/lnbitsUrl, or the implications of releasing a bounty.

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 0% and the description does not explain any of the 8 parameters. The phrase 'recipient Lightning address' vaguely references recipientLnurl or recipientLud16, but no parameter names, types, or usage details are provided.

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 action 'pay bounty to recipient Lightning address' with an explicit endpoint 'POST /api/bounty/release'. It distinguishes itself from siblings like submitBounty and bountyClaimWithdraw by indicating this is the release/payment step.

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?

The description provides no guidance on when to use this tool versus alternatives like submitBounty or bountyClaimWithdraw. It simply states the function without context, prerequisites, or exclusions.

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