cluster_summary

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

The description fully discloses the read-only, summary nature of the tool. Without annotations, it carries the burden of transparency and does so adequately, though it could mention that no changes are performed.

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 extremely concise: one sentence stating the output, followed by a directive. Every word earns its place.

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 there are no parameters and an output schema exists (though not shown), the description is sufficient for a simple summary tool. It lacks context about scope (e.g., cluster/namespace) but is adequate for its purpose.

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?

With no parameters, the baseline is 4. The description adds no parameter information, but none is needed as schema coverage is 100% due to zero parameters.

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?

The description clearly states it provides 'node and pod health totals plus the list of unhealthy pods' and positions itself as the entry point ('Start here'), distinguishing it from sibling tools like list_pods or node_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?

The phrase 'Start here' explicitly guides the agent to use this tool first for an overview, but does not provide when-not-to-use scenarios or mention alternatives.

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