node_status

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

No annotations provided, so description fully details behavior: blocks server-side, errors on timeout/terminal state, stops when only user action needed (wallet creation). This is comprehensive.

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?

Every sentence is informative; the description is front-loaded with the core purpose, then details on wait_for. No redundancy or fluff.

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 3-parameter tool with no output schema, the description fully covers what the tool returns and all parameter behaviors, making it self-contained for correct usage.

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 description adds significant context: explains each wait_for enum value, timeout range and behavior, and the return value implications for node_id.

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 tool's purpose: checking the status of a deployed Lightning node, returning specific fields like state, IP, and sync progress. It differentiates from sibling tools like deploy_node by focusing on status retrieval.

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?

Explicit guidance not to wrap in own polling loop and to use wait_for for blocking. Clearly explains when to use each wait_for option and the timeout behavior.

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