list_k8s_nodepools

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

The readOnlyHint annotation already covers safety, and the description adds a minor behavioral note about empty clusters. However, it does not disclose output format, pagination, or potential errors, so transparency is limited beyond the annotation.

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 with two sentences. The second sentence ('A cluster with no node pools runs no workloads.') is slightly redundant but adds a bit of context about typical usage without bloating the text.

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 the tool's simplicity and the absence of an output schema, the description provides no information about the return value or response structure. It is acceptable but not complete; agents might need to infer typical list behavior from sibling tools.

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 schema already provides full descriptions for both parameters (k8s_cluster_id and depth), and the tool description does not add any extra meaning or context to them. It neither clarifies nor expands on the parameter definitions.

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 resource ('in a Kubernetes cluster'), which precisely differentiates it from sibling list tools targeting other resource types. It is specific and 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 gives no explicit guidance on when to use this over alternatives, such as list_k8s_clusters or list_k8s_nodepool_nodes. It implies usage for retrieving node pools, but lacks direct comparative context.

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