lightning_unlock

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

With no annotations, the description carries the burden and usefully discloses session scope plus prerequisite operations. However, it does not describe failure behavior, security implications of the password, or whether unlocking persists until an explicit lock.

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 core purpose and prerequisites are front-loaded in two efficient sentences. The trailing 'earning_opportunities' tip is not needed for invoking this tool and slightly weakens focus, but the definition remains concise.

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 simple one-parameter unlock tool, the description gives enough context to call it correctly and explains its prerequisite role. It still lacks security, failure, and session-lifetime details that matter for a wallet-unlock operation without annotations.

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?

The single password parameter has 100% schema description coverage, including a sensitivity warning. The description adds no parameter details, so the baseline 3 applies.

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 states a specific verb and resource: unlock the Lightning wallet. It adds scope with 'for the current session' and distinguishes this from sibling tools like wallet_unlock by naming the Lightning wallet specifically.

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?

It clearly says when the tool is required: before paying, creating invoices, or enabling L402 auto-pay. It does not name alternatives or when-not conditions, but the prerequisite context is strong enough for correct selection.

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