hcloud_show_dws_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 statement about what detail fields are returned, error behavior for an unknown cluster_id, or region-scoping effects.

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, and the resource scope is stated before anything else. It is efficient but arguably undersized for a tool whose return contents are undocumented.

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 tool with full schema coverage and no output schema, the definition is minimally adequate. The gap is that nothing tells the agent what "details" comprise the response, which matters because no output schema exists to fall back on.

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 region and cluster_id are already documented in the schema. The description adds no extra meaning such as ID format, region naming conventions, or cross-region lookup behavior, 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 states a specific verb and resource ("Get details of a specific DWS ... cluster") and disambiguates the abbreviation, so an agent knows it is a single-resource read. It does not name the sibling hcloud_list_dws_clusters explicitly, so the list-vs-show distinction is only implied by "specific".

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?

"a specific ... cluster" implies the tool is used once a cluster_id is known, and the required cluster_id parameter reinforces that. However there is no explicit when-to-use, no prerequisite/permission note, and no named alternative such as hcloud_list_dws_clusters for discovery.

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