Get Kubernetes cluster

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint, so the safety profile is fully covered without the description. The description adds only that details=true pulls additional node and status data, but says nothing about the extra latency or payload size that flag implies.

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?

Two short sentences, front-loaded with the core action and followed immediately by the one useful parameter hint. Nothing is redundant or padded.

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 simple read-only getter with full annotation coverage and no output schema, this is nearly sufficient. A small gap remains: it does not indicate what fields are returned by default versus with details=true, leaving the agent to guess at response shape.

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 description coverage is 100%, so both parameters are already documented, including the source of the ID ('from list_kubernetes_clusters'). The description restates the details flag's effect in slightly different words, adding marginal value over the schema rather than new information.

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 names a specific verb and resource ('Get one Kubernetes cluster by ID'), which clearly separates it from the list-* siblings and from the config sibling. It does not explicitly name list_kubernetes_clusters or get_kubernetes_cluster_config, so the differentiation relies partly on the schema's cross-reference rather than the prose.

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: retrieve a single cluster when you already have an ID, and pass details=true for node/status data. There is no explicit when-to-use versus get_kubernetes_cluster_config or when the lightweight response is sufficient, so the agent must infer the alternative.

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