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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description still earns credit by disclosing that the kubeconfig is redacted (i.e., credentials are not returned) and by pinning the exact upstream call, GET /v2/kubernetes/clusters/{id}. It stops short of describing error/404 behavior for a missing or cross-region cluster.

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?

One front-loaded sentence carries the payload enumeration, then a short second clause carries the redaction caveat plus the raw endpoint. No filler, no restatement of the tool name, and the highest-value information comes first.

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?

There is no output schema, so the description's enumeration of returned fields (status, conditions, pools, network, firewall, CNI, apps) is exactly the compensating detail an agent needs to know what it will get back, and it flags the redacted kubeconfig. With only two parameters, full schema coverage, and a readOnly annotation, nothing material is missing.

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 cluster_id (UUID) and region (with defaults to CIVO_REGION and the regional-resource caveat) are already fully documented in the schema. The description only echoes the id in the endpoint path and adds nothing about parameter format beyond that, which is the expected baseline when the schema does the work.

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 ('Fetch one') and resource ('Kubernetes cluster') and then enumerates the returned facets (status, readiness, conditions, version and available upgrade, pools, network, firewall, CNI, marketplace apps). The word 'one' cleanly separates it from the sibling civo_list_kubernetes_clusters, so an agent can pick between them 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?

Usage is implied by 'Fetch one Kubernetes cluster' paired with the singular cluster_id requirement, and the endpoint template shows it is an id-addressed lookup. However, there is no explicit statement of when to prefer this over civo_list_kubernetes_clusters, nor any note about what happens when the id is unknown or the region is wrong.

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