wdk_get_node_info

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

With no annotations, description carries full burden. It accurately describes a read-only operation but does not disclose potential behaviors like failure modes on unreachable node, caching, or rate limits. Adequate for a simple info retrieval.

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-sentence description with no wasted words. First sentence lists what it returns, second sentence gives usage guidance. Perfectly concise and front-loaded.

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?

Given zero parameters and no output schema, the description is fairly complete: it explains the tool's purpose, output contents, and usage context. It could be enhanced by describing return format or structure, but for its simplicity it suffices.

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?

No parameters exist, so schema coverage is 100%. The description adds value by listing the output fields, which compensates for the empty schema. It provides meaning beyond the structured data.

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 gets RLN node identity and network summary, listing specific fields (pubkey, channels, lightning balance, peers). It distinguishes itself from sibling tools by explicitly positioning it as a first-step diagnostic tool.

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?

Explicitly instructs 'Call this first to confirm the node is reachable', giving clear when-to-use guidance. Lacks explicit when-not-to-use or alternatives, but context of siblings and the 'first' directive provides sufficient usage context.

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