hcloud_list_volumes

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond them — notably it never mentions that auto_paginate defaults to true and merges pages up to a soft cap, which is a real behavioral trait an agent should know before calling.

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?

Very short and front-loaded with the operation name, which is good, but the second sentence is pure redundancy with the first and with the tool name. Every sentence should earn its place, and this one does not.

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?

A seven-parameter list tool with an output-less schema and default auto-pagination deserves at least a note on what a Volume record contains and how pagination behaves. The description covers neither, leaving the agent to reverse-engineer behavior from parameter defaults.

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%, so all seven parameters (name, status, label_selector, sort, page, per_page, auto_paginate) are documented in the schema itself; this sets the baseline of 3. The description adds no meaning about filtering combinations or sort behavior beyond what the schema already provides.

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 the verb 'List' and the resource 'Volumes', so the basic operation is identifiable, but the second sentence ('Gets all existing Volumes that you have available') merely restates the name and adds no scope, differentiation, or detail. It does not distinguish this from siblings like hcloud_get_volume (single fetch) or hcloud_list_volume_actions.

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?

No guidance on when to use this versus hcloud_get_volume or hcloud_list_volume_actions, and no mention of prerequisites, filtering strategy, or the pagination defaults that materially affect usage. The intended use is only inferable from the name.

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