iaas_get_block_devices

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is fully covered by structured data. The description adds nothing beyond restating the HTTP path — no pagination behavior, no default page size, no indication of whether the full collection is returned or truncated.

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, which is good, but the first two lines are redundant restatements of the same phrase and the endpoint path is largely a duplicate of the annotations title. It is front-loaded but padded rather than informative.

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 parameterless-required list endpoint whose five query parameters are fully described in the schema and whose safety profile is fully described by annotations, nothing essential is missing. A richer description would be welcome but the agent has enough to invoke it correctly.

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% with five well-documented parameters (top, skip, count, filter, apiVersion), so the schema carries the semantic load. The description contributes no additional meaning about pagination or filter syntax; baseline 3 applies.

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 and resource ("Get all BlockDevices") and gives the underlying REST path, so the operation is identifiable as a collection list. However, it does not distinguish itself from the singular sibling iaas_get_block_device or from iaas_get_machine_disks, leaving the plural/singular split to be inferred from the name alone.

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 call this versus iaas_get_block_device (single-record fetch) or iaas_get_machine_disks, both of which return overlapping data. No prerequisites, no mention of how to page through a large collection.

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