remnawave_restart_all_nodes

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

Annotations provide readOnlyHint=false, idempotentHint=true, destructiveHint=false. Description adds context about force behavior: default force=true skips config-hash check, and force=false often skips restart. This goes beyond annotations, explaining the panel's decision logic. 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?

Two sentences, front-loaded with core purpose. No waste. Every sentence adds value: first defines the action, second explains the critical parameter behavior.

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?

With only one parameter and an output schema (not shown), the description fully covers the tool's behavior. The scope is clear, and the parameter semantics are well explained. No missing context for effective invocation.

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 description coverage is 0% per context, so description carries full burden. Description explains the force parameter's effect and default value, aligning with the schema's own description. Provides explicit usage guidance for the parameter, compensating for low schema coverage.

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 'Restart XRay on ALL enabled nodes', specifying verb (restart), resource (all enabled nodes), and scope (ALL). Distinguishes from sibling remnawave_restart_node by targeting all nodes rather than a single node.

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?

Implies usage: use force=false to allow hash-based skip, but no explicit guidance on when to choose this tool over remnawave_restart_node. The description explains the force parameter behavior but lacks explicit when-to-use or when-not-to-use compared to alternative tools.

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