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

readOnlyHint=true already establishes the safety profile, so the description's job is to add context beyond that — and it does, by disclosing the aggregated return payload (stacks, namespaces, drafts, recent warning/error events) and the fact that it collapses several read operations into one. It stops short of noting result size, truncation, or pagination behavior for large clusters, which is the only remaining gap.

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?

Three short sentences, each earning its place: one states purpose, one enumerates the payload, one gives usage priority and the alternative. The when-to-use guidance is front-loaded after the purpose statement, and there is no filler.

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?

With no output schema and only one well-documented parameter, the description carries the return-value burden and does so completely, listing each returned section. Combined with the first-call guidance, an agent has everything needed to call this correctly and interpret the result.

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?

There is a single parameter and schema coverage is 100%, including the schema-level hint to discover ids via list_clusters. The description adds nothing further about cluster_id, so the baseline 3 for a fully documented single-param schema is appropriate.

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?

States a specific verb and resource ('Get a full cluster overview') and then enumerates exactly what the overview contains (stacks with addon health, namespaces, drafts, warning/error events). This distinguishes it from siblings like get_cluster_details, list_stacks, and list_namespaces without the agent needing to open any schema.

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?

Explicit when-to-use ('Use this as your FIRST call when you need to understand the cluster state') and explicit alternatives ('Prefer this over calling list_stacks + list_namespaces + get_events separately'). This is exactly the routing guidance an agent needs to avoid three redundant calls.

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