list_nodes

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

With no annotations provided, the description carries the full behavioral disclosure burden. It states only the list action and resource, adding no information about return format, pagination, permissions, or whether the operation is globally scoped or cluster-scoped. The verb 'List' does imply read-only behavior, so there is no contradiction, but the transparency is otherwise minimal.

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 a single sentence with the key verb and resource front-loaded. Every word earns its place; there is no filler or repetition.

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 zero-parameter, no-output-schema tool, 'List cluster nodes' is nearly complete. The only slight gap is that it doesn't specify whether it returns all nodes in the current cluster or across clusters, and no return structure is mentioned; however, the low complexity keeps this from being a major deficiency.

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 tool has zero parameters and 100% schema description coverage (vacuously), so there is nothing for the description to add. The baseline of 4 for parameterless tools applies.

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 'List cluster nodes' uses a specific verb ('List') and a clear resource ('cluster nodes'), which unambiguously identifies a read-only enumeration operation. It also distinguishes from sibling tools such as list_projects and list_domains by the resource type.

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 intended use is implied by the resource name — use this tool when you need to see cluster nodes — but the description gives no explicit guidance about when to prefer it over related list tools, nor any exclusions or conditions. There are no sibling tools operating on nodes, so confusion is unlikely.

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