Restart Wazuh agents

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

The description explicitly discloses the side effect (interrupts monitoring) and the write-permission requirement, matching the destructiveHint and non-readOnly annotations. This goes beyond the annotations to explain the operational impact.

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 concise sentences, front-loads the action, and includes only essential context about side effects and permissions. No unnecessary wording.

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?

For a simple one-parameter, destructive-action tool, the description covers purpose, side effects, and prerequisites. The output schema is present, so no return-value explanation is needed.

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?

The schema already documents the single required parameter agent_ids with a clear description and example. The tool description adds no additional parameter-level detail, so baseline coverage is sufficient.

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 the action ('Restart'), the target resource ('one or more agents'), and its effect (interrupting monitoring). This distinguishes it from sibling tools like search, list, and scan operations.

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 useful context by noting the monitoring interruption and the WAZUH_ALLOW_WRITE=true requirement, so the agent understands when it is appropriate. It does not explicitly mention alternatives or when-not-to-use, but the purpose is clear enough.

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