hcloud_list_volumes

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

Annotations already declare readOnlyHint=true, openWorldHint=true and idempotentHint=true, so safety is covered. The description adds no behavioral context beyond the bare resource name — nothing on pagination behavior with limit, on whether results are region-scoped or cross-project, or on what happens when a region has no volumes.

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?

Four words, front-loaded with the verb and resource with zero padding. It is efficient rather than verbose, though the brevity reflects under-specification more than disciplined editing.

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 annotations, the minimum needed to call it is present. Still missing is whether region is mandatory in practice, whether results paginate, and how it differs from hcloud_show_volume, leaving the definition merely adequate.

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 both parameters are documented in the schema, making the baseline 3. The description contributes nothing to parameter meaning — it never mentions region scoping or the limit/max-results behavior.

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?

"List EVS disk volumes" gives a specific verb (List) plus the exact resource family (EVS disk volumes), which separates it from unrelated list tools like hcloud_list_snapshots or hcloud_list_volume_types. It does not, however, distinguish itself from the closely related hcloud_show_volume sibling or note how it relates to volume types/snapshots, so it stops short of full sibling differentiation.

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 guidance on when to use this tool versus alternatives such as hcloud_show_volume for a single volume, nor any stated prerequisites (e.g., that a region must be supplied). The agent must infer all usage conditions from the name and schema.

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