lightning_status

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

With no annotations present, the description carries full disclosure burden. It does add real signal by noting the balance is only returned 'if unlocked', so an agent knows to expect partial data in a locked state, and the enumeration of returned fields clarifies the read-only nature implicitly. It stops short of stating permissions, failure modes, or what happens when no wallet exists.

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-loaded with the core purpose and the returned-field list in a single tight sentence. The trailing 'Tip' about earning_opportunities is promotional filler that does not help an agent select or call this tool, though it costs little.

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?

Since there is no output schema and no annotations, the description must describe return values, which it does reasonably well by listing the five fields. However, it leaves ambiguous the distinction from sibling status tools (wallet_status, get_wallet_info) and says nothing about the locked-state edge cases beyond a parenthetical.

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 tool takes zero parameters, so there is nothing to disambiguate; baseline 4 applies. The schema is empty and the description correctly does not invent inputs.

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 ("Get the status of the embedded Lightning wallet") and enumerates the exact fields returned: unlock state, wallet id, balance, deposit address, Lightning address. It does not distinguish itself from sibling tools like wallet_status or get_wallet_info, which is the main gap.

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?

No guidance on when to call this versus wallet_status, get_wallet_info, or the lightning_unlock/lightning_lock siblings. The only routing hint is a promotional tip pointing at earning_opportunities, which is unrelated to selecting or invoking this tool.

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