setup_configure_lightning

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

Validates before saving is disclosed, but without annotations, more detail is needed: what 'saves' means (persistent?), overwriting behavior, validation failure consequences, and required permissions. The description is minimal.

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?

Two sentences, front-loaded with purpose, no redundant words. Efficiently conveys core functionality.

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?

Adequate for a configuration tool with clear schema, but no output schema or return value explanation. Lacks details on what happens after validation (e.g., success confirmation). Minimum viable for completeness.

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 covers 100% of parameters with descriptions. The description adds that lndconnect URL is an alternative to host+macaroon, but this doesn't significantly extend schema information, hence baseline 3.

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 it configures a Lightning node connection, lists accepted inputs (lndconnect URL or host+macaroon), and mentions validation. This distinguishes it from sibling tools like setup_check_status or setup_validate_credentials.

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 explicit guidance on when to use this tool versus alternatives. It implies it's the main configuration tool but doesn't mention prerequisites or exclusions like already-configured nodes.

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