hcloud_list_dds_flavors

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 that: no pagination behavior, no filtering semantics, and no indication of what a returned 'flavor/spec' contains.

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; the parenthetical disambiguation earns 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-only list tool with full schema coverage and no output schema, the minimum is met, but an agent gets no sense of result contents (CPU/memory/disk specs) or whether results are scoped to a region.

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 the schema itself documents both parameters (engine, region required). The description mentions neither parameter and adds no meaning such as whether engine filters results or defaults to MongoDB, so the baseline 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 clear verb ('List') plus the specific resource ('DDS (MongoDB) instance flavors/specs') and even expands the DDS acronym, which distinguishes it from the many sibling flavor-listing tools (rds_flavors, dws_flavors, gaussdb_flavors, dcs_flavors, elb_flavors). It stops short of explicitly naming those siblings as alternatives, so it is clear but not fully differentiated by routing language.

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 explicit when-to-use guidance, no prerequisite notes (e.g., that it is typically called before creating a DDS instance), and no mention of which sibling flavor lister to pick for other engines. Usage is only implied by the resource name.

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