hcloud_show_node_pool

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not mention region scoping as a prerequisite, what happens if the pool does not exist, or any notable return characteristics.

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. It is efficient, though its brevity reflects under-specification rather than tight curation of substantive 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 lookup with fully documented required parameters and no output schema, the description is adequate but thin. It leaves the caller without the ID-sourcing workflow or any indication of what the returned details contain, which an agent planning a multi-step node pool inspection would benefit from.

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 each of the three required parameters is documented in the schema and the baseline is 3. The description contributes no extra meaning, such as whether nodepool_id must belong to the given cluster_id or whether region must match the cluster's 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 states a specific verb and resource ('Get details of a specific CCE node pool'), which is unambiguous against sibling list tools like hcloud_list_node_pools. It does not explicitly name the close sibling, but the singular 'specific ... node pool' versus list semantics is clear from the text.

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 beyond the implicit single-object fetch. It never tells the agent it needs a nodepool_id obtained from hcloud_list_node_pools, nor does it state that this tool is the follow-up to the list call. The agent must infer the workflow entirely.

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