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

readOnlyHint=true already establishes this as a safe read, lowering the bar. The description adds useful context by listing what the payload contains and noting it works without an active cluster selection, but it says nothing about lookup failures, ambiguity when both name and ID are supplied, or response shape details.

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 compact sentences with the purpose front-loaded, followed by the payload contents and a behavioral note. The trailing 'and more' is slightly loose but the overall structure is efficient and easy to scan.

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 lookup with fully documented parameters and no output schema, the description does the work of summarizing return fields. The only real gap is disambiguation from the several other cluster-inspection siblings, which is not addressed.

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 coverage is 100% with both parameters fully documented, so the baseline is 3. The phrase 'by name or ID' reinforces the two lookup keys but adds no syntax, format, or precedence information beyond what the schema already provides.

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 detailed information about a specific cluster by name or ID') and enumerates the returned fields (state, environment, Kubernetes version, node count, agent status). It does not name any of the closely related siblings such as cluster_describe, get_cluster_status, or get_cluster_insights, so an agent must infer the distinction.

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?

Usage is implied through 'by name or ID' and the note that it 'Works even when no cluster is selected,' which hints at a context where a cluster may not be selected. However, there is no explicit when-to-use versus cluster_describe/get_cluster_status guidance or any stated exclusions.

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