cloud_create_volume

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

No annotations are provided, so the description must carry the full burden. It only mentions input constraints (size unit, location/server requirement) but does not disclose any behavioral traits like idempotency, error handling, or what the call mutates. Output schema exists but is not referenced.

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?

Two sentences, front-loaded with the action, no irrelevant information. Every word 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?

Given 7 parameters, 0% schema coverage, no annotations, and an output schema, the description is too brief. It fails to explain parameter purposes beyond two, return value expectations, or error conditions. An agent would lack sufficient information to invoke the tool correctly in many scenarios.

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 0% (no descriptions in schema). The description adds value for 'size' (unit GB) and the required relationship between 'location' and 'server'. However, it does not explain other parameters like 'format', 'automount', 'labels', leaving them ambiguous.

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 'Create a volume' (verb+resource) and adds that size is in GB and either location or server is required. This differentiates it from sibling tools like cloud_attach_volume or cloud_resize_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 constraint (either location or server required) but lacks guidance on when to use this tool vs alternatives, such as when to create vs attach a volume, or implications of choosing location vs server.

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