k8s_list_nodes

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

No annotations are present, so the description must carry the safety and behavioral burden. 'List' communicates read-only intent and the Ready-condition detail states the returned scope, but there is no disclosure of session/authentication requirements or behavior on failure.

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 entire description is one short sentence, with the action and output detail front-loaded. There is no filler or repeated schema content.

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 read-only listing with one optional defaulted parameter and an output schema, the description is nearly sufficient. It lacks explicit context about the session parameter and connection prerequisites, so it is adequate but not complete.

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 provides no description for session_name (0% coverage), and the tool description never mentions it. The description does not clarify whether session_name selects a cluster/connection or how it relates to the k8s_connect sibling.

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 uses the specific verb 'List' with the resource 'nodes,' and adds the output detail 'Ready condition,' so an agent can tell this apart from sibling list tools like k8s_list_pods or k8s_list_namespaces. The name and description align exactly.

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?

There is no guidance on when to use this tool over alternatives, nor any mention of prerequisites such as an active k8s_connect session. The only hint is the resource name itself, which makes the choice obvious but leaves context unstated.

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