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

readOnlyHint=true already declares the safety profile, so the description's job is to add context beyond that. It does so usefully by disclosing the exact shape of the return payload, which matters because there is no output schema. It still omits whether the usage percentages are point-in-time or averaged, and whether results are cached.

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 sentences with zero filler: purpose, return contents, and routing to alternatives, in that order. Every sentence earns its place and the most decision-relevant information is front-loaded.

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 read-only, single-parameter tool with no output schema, the description covers purpose, returns, and sibling routing, which is nearly everything an agent needs. Minor gaps remain around freshness/aggregation window of the resource usage figures and any cluster-id validity constraints.

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?

The single parameter (cluster_id) has 100% schema description coverage, including UUID format and guidance to discover ids via list_clusters, so the schema carries the load. The description adds no parameter-level meaning beyond that, which is the expected baseline when coverage is high.

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+resource ('Get cluster health overview') and immediately enumerates the returned contents (node ready/not-ready counts, pod counts by status, resource usage percentages). It also names the siblings it is not, so an agent can separate it from get_pods/get_deployments without opening a 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?

Explicitly scopes usage ('quick health check') and routes to alternatives ('For detailed resource lists, use get_pods/get_deployments instead'). However, it does not distinguish itself from the much closer siblings in this large toolset such as get_cluster_details, cluster_describe, get_cluster_attention_summary, or get_cluster_insights, leaving the main ambiguity unresolved.

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