hcloud_show_gaussdb_instance

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so safety and repeatability are covered. The description adds nothing beyond them — no note on what happens if the instance_id is invalid, no indication of the returned detail set, no mention that region must match the instance's actual region.

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; the '(openGauss)' parenthetical is the only extra detail and it is genuinely disambiguating. It is efficient but extremely thin, offering nothing to structure beyond the purpose statement.

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 read-only show tool with two fully documented required parameters, the minimum needed to call it is present. However, with no output schema, the description should say something about what fields a 'details' response contains; that gap is left entirely unaddressed.

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 parameters are documented ('Region', 'GaussDB instance ID'). The description adds no extra meaning such as ID format or how to source the instance_id, making the baseline 3 appropriate.

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?

States a specific verb ('Get details') and a specific resource ('a specific GaussDB (openGauss) instance'), and the singular 'specific' plus the parameter set makes clear this is a single-object read. It does not explicitly name the sibling hcloud_list_gaussdb_instances or state that listing precedes it, so it falls short of full sibling differentiation.

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 at all: no statement of alternatives (hcloud_list_gaussdb_instances, hcloud_list_gaussdb_flavors), no prerequisite that an instance_id must first be obtained, and no exclusion conditions. Only the show-vs-list naming convention implies usage.

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