node_list

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

readOnlyHint=true already covers the safety profile, and the description adds genuine context by naming the fields returned (name, status, roles, version, schedulable, age). It stops short of describing pagination or output format, but adds real value 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?

Front-loaded [READ] + verb + resource + returned fields, followed by a compact Args note. Efficient, with the return columns parenthetically structured rather than padded.

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 one-param read tool with no output schema and readOnlyHint set, the description is complete enough: it covers purpose, returned fields, and the param's default behavior. Only minor absence of pagination/ordering details.

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 coverage is 0% for the single target param, but the description compensates by defining it as a k8s target name from config and explaining that omitting it falls back to the default. This adds meaning the bare schema does not carry.

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 (cluster nodes), and even enumerates the returned columns (name, status, roles, version, schedulable, age). This clearly distinguishes it from siblings like node_describe, node_top, and cordon_node.

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 [READ] tag and List framing imply a read-only enumeration, but the description gives no explicit when-to-use guidance versus node_describe or node_top. Usage is inferable but not spelled out.

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