ibmcloud_ks_clusters

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'List Kubernetes clusters' and does not mention output format, scope (e.g., account or resource group), pagination, or read-only semantics. This is minimal and lacks detail beyond what the tool name 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?

The description is extremely concise at three words with no filler, making it easy to parse. However, it is slightly under-specified because it does not mention the optional provider filter, but the schema covers that, so the brevity is mostly appropriate.

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 list tool with one optional parameter and no output schema, the description is minimally viable. It is missing information about returned data, account/region scope, and prerequisites such as login or target context, but the schema fills in the filter option.

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?

The input schema covers the only parameter 'provider' with a description 'Filter by provider (vpc-gen2, classic)', providing 100% schema coverage. The tool description adds no parameter information, so the baseline of 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?

The description 'List Kubernetes clusters' uses a specific verb and resource, clearly indicating the action. It is distinguishable from the singular sibling 'ibmcloud_ks_cluster' by pluralization, but it does not explicitly state that distinction, so it stops short of a 5.

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?

No guidance is provided on when to use this tool versus alternatives like 'ibmcloud_ks_cluster' for details or 'ibmcloud_ks_cluster_create' for creation. The description only states the basic action, leaving the agent without context for selection.

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