hcloud_show_cbr_vault

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

The annotations already establish a read-only, idempotent, open-world operation, and the description is consistent with them. It adds single-vault detail-retrieval scope but no further context about not-found behavior, response scope, or service-side constraints.

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?

The single front-loaded sentence is direct and contains no unnecessary wording. Expanding CBR to 'Cloud Backup and Recovery' adds useful clarity without making the description verbose.

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 read-only lookup with two documented required parameters, the description, schema, and annotations provide enough information to invoke the tool correctly. Explicit ID-discovery guidance and a brief response or error-behavior note would make it more complete, especially without an output schema.

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 baseline of 3 applies. 'Specific ... vault' loosely reinforces the role of vault_id, but the description adds no region selection or identifier-format guidance beyond the schema.

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 clear verb and resource: retrieving details for one specific CBR vault, and usefully expands the CBR acronym. It implies differentiation from hcloud_list_cbr_vaults but does not explicitly define that boundary.

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?

The phrase 'a specific ... vault' implies use when the target vault is already known, rather than when browsing vaults. However, there is no explicit when-to-use guidance or pointer to hcloud_list_cbr_vaults for discovering a vault ID.

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