cluster_health

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

No annotations provided, but description includes '[READ]' to indicate read-only. It explains what the tool reports, but could add more on idempotency or error conditions.

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?

Extremely concise: one sentence plus brief Args list. Front-loaded with purpose and action. No unnecessary information.

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?

Given no output schema, description provides a reasonable overview of returned information (services, resiliency, upgrade state). Could be more detailed, but sufficient for a simple health query.

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 has 0% description coverage; the description compensates by explaining the source and usage of both parameters (cluster_ext_id from cluster_list, target from config).

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 clearly states verb 'READ' and resource 'cluster health', listing specific aspects (services, resiliency, upgrade state). It distinguishes from siblings like cluster_health_rca and cluster_utilization.

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 clear parameter guidance: cluster_ext_id from cluster_list, target from config. However, does not explicitly state when to prefer this over alternatives like cluster_health_rca.

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