k8s_list_kubernetes_node_pools

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

With no annotations, the description must disclose behavioral traits itself. It mentions that the identifier can be a label or UUID, which is useful, but does not state that the operation is read-only, potential error conditions, or pagination behavior. The description gives minimal insight beyond the core listing action.

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 concise and well-structured: a one-sentence purpose, a note on identifier resolution, and a clean args/returns breakdown. Every sentence serves a purpose with no fluff or redundancy. The key information is front-loaded.

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?

Given that an output schema exists, the description does not need to explain return values. However, it lacks any mention of prerequisites, potential failure modes (e.g., cluster not found), or whether the list is paginated. For a straightforward list tool, this is adequate but not comprehensive; there is room to mention that the cluster must exist or that the list includes configuration and status, which it does.

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 provides only a bare string type with no description, so the description carries the burden of explaining the parameter. It clearly states that the parameter is 'The cluster label or ID' and adds 'Smart identifier resolution: use cluster label or UUID,' which adds meaningful context beyond the schema. This is helpful, though it could go further with format details.

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 clearly states the action ('List all node pools') and the target resource ('for a Kubernetes cluster'). It distinguishes itself from sibling tools like k8s_get_kubernetes_node_pool by specifying the list behavior and scope. The verb and resource are unambiguous.

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 description does not explicitly state when to use this tool versus alternatives such as k8s_get_kubernetes_node_pool or k8s_list_kubernetes_nodes. It provides a hint about identifier resolution but no guidance on selecting this over similar tools. The context implies a listing use case, but exclusions or comparisons are absent.

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