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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds non-obvious behavior: the pagination envelope shape, that kubeconfigs are redacted, and the underlying Civo endpoint — all useful context beyond the annotations.

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?

Front-loaded with the resource and scope, followed by pagination shape, a redaction note, and the raw endpoint. Slightly dense but each clause carries information and there is no filler.

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 takes on the burden of describing return values and does so, listing key fields plus the pagination envelope and the kubeconfig redaction. Nothing critical is missing for a read-only list call.

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 page, per_page and region semantics (including the CIVO_REGION default and region code examples) are already fully documented in the schema. The description adds nothing parameter-specific beyond that baseline.

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 (List) and resource (Kubernetes K3s/Talos clusters) scoped to a region, and enumerates the returned fields (status, version, node pools, API endpoint, installed applications). It is clearly distinguishable from the singular sibling civo_get_kubernetes_cluster.

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 region parameter text points to civo_list_regions and notes resources are regional, which implies when to pass a region. However there is no explicit statement of when to prefer this over civo_get_kubernetes_cluster or other list tools.

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