hcloud_show_cce_cluster

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 them - no note on what happens if the cluster_id is unknown, no mention of region scoping behavior, and no indication of response shape.

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. Its brevity is appropriate in form, though the extreme terseness leaves informational gaps that are penalized elsewhere rather than here.

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 is the only place an agent could learn what a cluster detail record contains, and it says nothing. For a show/detail tool with two required identifiers, this leaves the agent guessing about returned fields and error conditions.

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 both required parameters (region, cluster_id) are documented in the schema itself. The description adds no extra meaning such as ID formats or where to obtain the cluster_id, so the baseline of 3 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 gives a verb ("Get details") and a resource ("a specific CCE cluster"), so it is not tautological. However, "details" is vague about what is actually returned, and nothing distinguishes it from siblings such as hcloud_list_cce_clusters or hcloud_list_cce_nodes beyond the implicit singular/plural split.

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 instead of hcloud_list_cce_clusters, and no prerequisites or exclusions are stated. The agent must infer that a cluster_id from the list tool is required before calling.

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