hcloud_show_mrs_cluster

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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context of its own — nothing about what the returned details include (status, nodes, version), latency, or cross-region considerations, despite region being a required qualifier.

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 short sentence with zero filler, front-loading the verb and resource. Nothing in it is redundant with the title in a wasteful way, and no sentence fails to earn its place.

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 two-parameter read tool whose annotations and fully-documented schema cover safety and inputs, and with no output schema to explain, the description is nearly sufficient. A brief note on what the detail payload contains would complete it, but nothing needed for correct invocation is missing.

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% for both parameters (region, cluster_id), so the schema already carries the semantics and a baseline of 3 applies. The description contributes only the word "specific," which reinforces that cluster_id selects one cluster but adds no format or scoping detail.

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 uses a specific verb ("Get details") and a named resource ("a specific MRS (MapReduce Service) cluster"), and the word "specific" distinguishes it from the sibling hcloud_list_mrs_clusters. It does not name that sibling explicitly, so sibling differentiation is implied rather than stated.

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: an agent can infer this is the tool for fetching one cluster once it has a cluster_id, versus listing many. There is no explicit statement of when to use this instead of hcloud_list_mrs_clusters, nor any prerequisite or error guidance (e.g., what happens with an unknown cluster_id).

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