Get Node Health

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

Discloses key behaviors: returns structured conditions, orders unhealthy first, includes remediation hints, and is read-only. Without annotations, this is good transparency. Mild ambiguity about whether it applies to all nodes or a specific node.

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?

Single sentence packed with useful information: conditions type, order, hints, and safety. 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?

Description adequately covers purpose and key features. Lacks explicit statement of whether it covers all nodes or a specific node, but for a zero-parameter tool, it is reasonably 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?

No parameters, so schema coverage is 100%. Description adds no parameter info, but none is needed. Baseline 4 justified by high coverage; no issues.

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 returns structured node conditions (Ready, memory/disk/PID/network pressure) with unhealthy nodes first and short remediation hints. Distinguishes from sibling tools like list_nodes which likely only list nodes without detailed health.

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 it's for diagnosing node health, but does not explicitly say when to use vs. alternatives (e.g., list_nodes). Lack of explicit when-not or alternative references, but context is clear enough.

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