iaas_resize_block_device

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, so the agent knows this is a non-idempotent mutation. The description adds nothing beyond that: it does not say whether capacity can be shrunk, whether the device or attached machine must be in a particular state, or what happens on failure. No contradiction with annotations.

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?

It is short and front-loaded, but two of the three lines are redundant: the second restates the first and the third repeats the endpoint already given in the annotations title. Nothing is long-winded, but little of the text earns its place.

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 mutation tool with no output schema and no operational detail, the description is too thin. An agent cannot tell from it what a successful resize returns, whether quota/SDRS constraints apply (only hinted at in the schema), or how long the operation takes.

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% and all four parameters (id, capacityInGB, useSdrs, apiVersion) carry clear descriptions, so the schema does the work. The description contributes no additional parameter meaning, which matches the baseline of 3 when structured fields are already complete.

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 says "Resize BlockDevice" and "Resize operation on block device," which only restates the tool name and title without adding scope or detail. It never explains what resizing means here (capacity change, provider constraints) or how it differs from siblings such as iaas_resize_machine or iaas_create_block_device.

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 when-to-use guidance, no prerequisites, and no mention of alternatives in a list containing iaas_resize_machine and iaas_delete_block_device. The only extra content is the REST path, which does not help an agent decide when to select this tool.

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