hcloud_list_server_block_devices

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 the server-scoping behavior, which is useful, but says nothing about pagination, whether detached volumes are excluded, or what identifies the devices in the response. With annotations carrying safety, this is an adequate but thin addition.

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 resource and its scope are stated immediately. Nothing is wasted or buried.

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 tool with no output schema and strong annotations, the description is minimally sufficient. However, an agent cannot learn whether the result includes device names, sizes, or attachment status, nor whether it covers only currently attached volumes.

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% and there are only two required parameters, so the baseline is 3. The description's mention of 'ECS server' reinforces that server_id refers to a server (not a volume), but adds no format, region-vs-server relationship, or filtering semantics 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?

States a specific verb (list) and a scoped resource (block devices/volumes attached to an ECS server), and clarifies the volume equivalence in parentheses. This implicitly separates it from hcloud_list_volumes (account-wide) and hcloud_list_server_interfaces, though neither sibling is named explicitly.

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 prefer this over hcloud_list_volumes, hcloud_show_server, or hcloud_show_volume, and no stated prerequisites (e.g., server must exist, permissions needed). The agent must infer the use case from the scope wording alone.

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