k8s_list_kubernetes_nodes

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

With no annotations, the description carries the behavioral disclosure burden. It adds useful context by explaining 'Smart identifier resolution: use cluster/node pool labels or UUIDs,' which tells the agent how identifiers are interpreted. It also discloses the return content ('nodes with status and configuration'), though it does not cover pagination, limits, or permission requirements.

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 compact and well-organized: a one-line purpose, a useful identifier-resolution note, a short Args section, and a Returns section. No filler or redundant content is present, and the key purpose 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?

For a low-complexity list operation with an output schema, the description covers the required parameters, the identifier behavior, and the general return shape. It could be slightly more complete by explicitly noting the operation is read-only or by naming sibling alternatives, but nothing essential for calling the tool correctly is missing.

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 0%, so the description must compensate. It does: both parameters are explained as 'cluster label or ID' and 'node pool label or ID,' and the intro adds that labels or UUIDs are accepted. This adds real meaning beyond the plain string type in the schema, though it stops short of giving concrete format examples.

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 states a specific action ('List all nodes') and a specific scope ('in a specific node pool'), making the tool's purpose immediately clear. It distinguishes itself from siblings like k8s_get_kubernetes_node (single node) and k8s_list_kubernetes_node_pools (pools) by the resource and scope it targets.

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 implies the tool should be used when an agent needs all nodes belonging to a particular node pool, but it does not explicitly name alternatives or state when not to use it. There is no direct comparison to k8s_get_kubernetes_node or k8s_list_kubernetes_node_pools, leaving some routing to inference.

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