cloud_resize_volume

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

With no annotations provided, the description carries the full burden. It discloses that resizing is only a grow operation and that filesystem growth happens online, implying no downtime. However, it fails to mention prerequisites, error handling (e.g., attempting to shrink), or whether the volume must be attached.

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?

The description is extremely concise (two sentences) with no wasted words. It front-loads the core action and adds critical constraints, making it easy to parse quickly.

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?

Given the presence of sibling tools like cloud_update_volume and the lack of parameter semantics, the description is too brief. It does not cover return values (though output schema exists), prerequisites, or potential side effects (e.g., cost or action triggers). More context is needed for complete agent understanding.

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?

The input schema has 0% description coverage for its two parameters ('volume_id' and 'size'). The description does not explain what 'size' represents (e.g., new size in GB, increment) or any valid ranges, leaving the agent without sufficient meaning from the description.

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 clearly states 'Resize a volume', specifying the verb and resource. It adds constraints 'Can only grow, not shrink' and 'Filesystem grow happens online', which help distinguish it from siblings like cloud_update_volume. However, it does not explicitly differentiate from cloud_update_volume.

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?

The description provides a key limitation ('Can only grow, not shrink') but does not give explicit guidance on when to use this tool versus alternatives like cloud_update_volume or when shrinking is needed. The usage context is implied but not fully articulated.

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