Create a volume

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

No annotations are provided, so the description carries full burden. It usefully discloses that the operation is billed and that 'confirm true' is required — critical behavioral context for a paid mutation. It doesn't state reversibility, idempotency, or permission needs, but the billing/confirm disclosure is the most important trait here.

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?

Three short sentences, front-loaded with the action, then cost, then placement options. Efficient, though the placement clause is compressed to the point of ambiguity (server vs. location as alternatives).

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 7-param paid mutation with no annotations and no output schema, the description covers the essential cost/confirm gate but omits permission requirements, what the returned volume looks like, and clear guidance on choosing server vs. location. Adequate but with clear gaps.

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%, so the schema already documents all seven params including the confirm flag's billing note. The description restates the confirm requirement but adds no syntax or semantics beyond the schema, so 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 a specific verb+resource ('Create a Hetzner Cloud volume'), clearly distinguished from sibling operations like cloud_delete_volume or cloud_attach_volume. The core action is unambiguous, though the trailing 'Attach to a server or place in a location' reads like usage guidance rather than purpose.

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?

Implies how to place the volume (server vs. location) but doesn't explicitly say when to use this tool versus cloud_attach_volume or when to prefer server-attach over location. No when-not guidance or prerequisites beyond the confirm flag.

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