hcloud_list_cbr_vaults

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 by structured data. The description adds nothing beyond that: it does not say how pagination behaves, whether the region parameter narrows results, or what identifying fields each vault entry carries.

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 or redundancy. It is efficient, though the space saved is not used for any disambiguation that would help selection.

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 three-parameter read-only list tool with a fully documented schema and no output schema, this is minimally sufficient. It stops short of telling the agent how to scope results by region or what a returned vault looks like, which would matter when choosing between this and hcloud_show_cbr_vault.

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 coverage is 100% with all three parameters (limit, offset, region) described inline, so the schema carries the semantics. The description adds no extra meaning, such as whether region is mandatory or how limit/offset interact, which is the expected baseline when the schema is fully documented.

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 specific verb ('List') and resource ('CBR vaults') and expands the CBR acronym, so an agent knows exactly what collection is returned. It does not, however, distinguish this from the sibling hcloud_show_cbr_vault (single vault) or the adjacent hcloud_list_cbr_backups / hcloud_list_cbr_policies collections.

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 and no mention of alternatives; an agent must infer from the name alone that this lists vaults rather than fetching one vault or listing backups/policies. No prerequisites (e.g. that a region must be supplied to scope results) are stated.

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