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

Annotations already establish readOnlyHint=true, and the description adds real behavioral context beyond that: the kubeconfig is redacted, and the underlying API call (GET /v2/kubernetes/clusters/{id}) is disclosed. It does not mention auth/permission requirements or error behavior, so it stops short of a 5.

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?

A single dense sentence front-loads the resource, then lists returned fields and the security-relevant redaction note before the API endpoint. It is longer than most definitions but every clause describes a distinct output facet, which is justified in the absence of an output schema.

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, the description compensates by enumerating what is returned and flagging the redacted kubeconfig. Combined with full schema param coverage and read-only annotations, it is essentially complete; only pagination/error and auth details are absent, which are minor here.

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 and region are already fully documented in the schema (including the region default and examples). The description adds no parameter-level syntax or format detail, so the baseline 3 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 (Fetch) and resource (one Kubernetes cluster), then enumerates the returned facets (status, readiness, conditions, version, pools, network, firewall, CNI, marketplace apps). An agent can distinguish this from civo_list_kubernetes_clusters without opening either 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?

The singular 'one cluster' plus a required cluster_id implies the use case (retrieve details for a known cluster id), but no explicit when-to-use/when-not guidance and no sibling alternative is named. The region parameter's dependency on CIVO_REGION is only in the schema, not the description.

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