list_installed_nodes

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

Discloses the tool uses HTTP API or CLI fallback, and that cm-cli returns only names. No annotations provided, but the listing nature implies read-only. Could mention if it requires any specific permissions or has rate limits, but not necessary given context.

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, no wasted words. Front-loaded with main purpose, then technical details. Highly efficient.

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?

No output schema exists, but description mentions return content (version, state, names). Covers all parameters and use cases. Could optionally mention pagination or ordering, but not essential for this tool.

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 value by explaining the API/CLI distinction and error conditions for remote mode. The schema already describes the 'mode' and 'useCmCli' parameters, but description provides additional operational context.

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?

Description clearly states the tool lists installed custom node packs with version and enabled/disabled state. It distinguishes from sibling tools like 'get_node_pack_details' or 'install_custom_node' by focusing on listing with state details.

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?

Describes when to use default vs imported modes and explains the fallback behavior of cm-cli. Provides error context for remote use. No explicit comparison to alternative tools for similar tasks.

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