wazuh_cluster_node_stats

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

No annotations are provided, so the description must carry the full burden. It clearly states the tool retrieves statistics and enumerates the data categories (EPS, queues, daemon, utilization). This is sufficient to convey that the operation is read-only and diagnostic. Additional details about error handling or limits are not needed given the simplicity.

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 with zero waste. The first sentence states the action and resource, the second adds value by listing examples and use case. Front-loaded and 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?

For a single-parameter tool with an output schema, the description is complete. It explains the tool's purpose, the kind of data returned, and its utility. No gaps remain given the sibling context and available structured metadata.

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 100%, with a clear description of 'node_id' including examples. The description does not add new information beyond stating it is 'for a specific Wazuh cluster node', which is already implicit in the parameter name and schema. Per guidance, baseline 3 is appropriate when schema already documents parameters well.

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 uses specific verb 'Get detailed statistics' and identifies the resource as 'a specific Wazuh cluster node'. It lists the types of data shown (EPS, queue sizes, daemon status, resource utilization), clearly distinguishing it from sibling tools like wazuh_cluster_status which likely covers cluster-wide stats.

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 phrase 'Essential for diagnosing cluster imbalances' provides a clear use case. While it does not explicitly state when not to use or list alternatives, the purpose is specific enough that an agent can infer it is for deep-dive node analysis versus higher-level cluster overview tools. This is adequate but not exhaustive.

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