hcloud_list_cce_nodes

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds nothing beyond that: no mention of pagination, result volume, filtering, or what a node record contains, so it contributes essentially no behavioral context of its own.

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?

A single front-loaded sentence with zero filler or redundancy. It is efficient, though the brevity reflects under-specification rather than disciplined economy.

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?

There is no output schema, so the description should carry the burden of explaining what comes back, pagination behavior, and how region and cluster_id relate to the returned nodes. None of that is present, leaving the tool under-described for an agent that needs to call it correctly.

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 100% and both parameters are required, so the baseline of 3 applies. The schema descriptions are bare labels ('Region', 'Cluster ID'), and the description adds no format, sourcing, or scoping detail beyond them.

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 gives a specific verb and resource ('List nodes') scoped to a CCE cluster, which is enough to distinguish it from cluster-level or node-pool-level siblings in principle. However it never names hcloud_list_node_pools or hcloud_list_cce_clusters, so the boundary between 'nodes', 'node pools' and 'clusters' is left to the agent to infer.

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 when-to-use guidance: no statement of prerequisites (an existing cluster, valid region scope), no exclusions, and no reference to alternatives such as hcloud_show_cce_cluster or hcloud_list_node_pools. The agent must infer the call context purely from the name.

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