toggle-node-module

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

No annotations are provided, so the description carries full burden. It only states the action (enable/disable) without disclosing side effects (e.g., need for restart, permissions, impact on flows). This is insufficient for safe invocation of a mutation tool.

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?

The description is two sentences: the first states purpose, the second lists args with examples. It is efficient, front-loaded, and contains no redundant information.

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 the tool is simple and has no output schema, the description conveys the core action. However, it lacks details on return value, immediate effect, or any preconditions. Sibling tools like 'get-node-detailed-info' have richer descriptions, making this one slightly under-specified.

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% with descriptions for both parameters. The description adds value by providing concrete examples ('node-red/inject' for module, 'true' for enabled), clarifying the expected format beyond the schema's general 'Node module name'.

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 action (enable or disable) and the resource (specific node module) with a concrete example. It distinguishes from sibling tools like 'toggle-node-module-set' which operates on a set, and 'install-node-module' which is for installation.

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?

The description does not explicitly state when to use this tool versus alternatives like 'toggle-node-module-set' or 'install-node-module'. It provides example arguments but lacks guidance on context or prerequisites, making it minimally adequate.

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