remnawave_restart_node

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

Discloses mutation, brief interruption, and effects of each parameter (force skips hash check, force_cycle disables/re-enables). Complements annotations with no contradiction.

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?

Three sentences, front-loaded with purpose and warning. Every sentence adds value. No wasted words.

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?

Fully explains the tool's effect, parameter choices, and trade-offs. Given 3 parameters and output schema, it is complete.

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 already describes parameters; description adds behavioral context (e.g., 'force_cycle heavier, re-establishes connection'). Adds value beyond schema.

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?

Clearly states it restarts XRay on one node, distinguishes from restart_all_nodes and disable/enable siblings. Explains different modes of operation.

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?

Provides when to use default, force, and force_cycle modes. Could explicitly mention when not to use (e.g., for multiple nodes), but gives clear context.

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