hcloud_list_gaussdb_instances

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: no statement about pagination behavior, default limits, cross-region scope, or what a listing actually contains, which is the remaining value it could have supplied.

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 fragment with zero wasted words, and the resource is front-loaded. It is efficient but so terse that it has no room for structure (no conditions, no scope qualifiers), which keeps it just short of a top mark.

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?

The tool is simple (one required param, all params documented, no output schema), so the minimal description is not disastrous. Still, it omits what a caller would want for a list operation — pagination defaults, region scoping, and the fact that filtering is available via db_type — leaving real gaps for an otherwise straightforward tool.

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 all four parameters (region, limit, offset, db_type) are documented in the schema, making a baseline of 3 appropriate. The description contributes no additional semantics such as valid db_type values, default page size, or whether region is mandatory for scoping.

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 (List) and resource (GaussDB/openGauss instances), and the parenthetical clarifies the engine, so an agent knows exactly what collection is enumerated. It does not, however, differentiate from adjacent siblings such as hcloud_list_gaussdb_flavors, hcloud_list_gaussdb_datastores, or hcloud_show_gaussdb_instance, so sibling disambiguation is left entirely to the tool name.

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, no mention of prerequisites such as a required region or credentials, and no pointer to alternatives (e.g. use hcloud_show_gaussdb_instance for a single instance's details). The agent must infer routing from the name alone.

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