hcloud_list_node_pools

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 only the cluster-scoping context and says nothing about result volume, pagination, or whether an empty list is possible for a cluster with no pools — minimal value on top of structured data.

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 no filler or redundancy; nothing needs trimming. It is arguably too terse rather than bloated, which is penalized under contextual completeness instead.

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 two-parameter read-only list tool with full schema coverage and clear annotations, this is close to adequate. The remaining gap is that with no output schema, the agent gets no signal about what the returned node pool objects contain or how large the result may be.

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%, so the baseline is 3. However, the schema descriptions are bare labels ('Region', 'Cluster ID') and the prose does not enrich them — no format hints, no note on whether cluster_id must belong to the given region.

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 node pools') plus a scoping qualifier ('in a CCE cluster'), which separates it cleanly from unrelated list tools such as hcloud_list_pools (ELB) or hcloud_list_cce_nodes. It stops short of naming the closest siblings (hcloud_show_node_pool, hcloud_list_cce_clusters), so differentiation is by noun alone.

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?

Usage is only implied: the agent can infer it needs an existing CCE cluster (region + cluster_id) before calling. There is no explicit statement of when to prefer this over hcloud_show_node_pool for a single pool or over hcloud_list_cce_nodes for node-level detail.

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