pve_disk_resize

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

Discloses mutation, grow-only constraint, destructive nature of shrink, dry-run behavior, async execution, and return of UPID. No annotations provided, so description carries full burden and covers key traits.

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?

Extremely concise with three sentences, front-loaded with 'MUTATION', and every sentence adds necessary information without redundancy.

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 and async behavior with output schema, the description covers essential behavioral context. Missing parameter details are partially compensated by example, but overall complete enough for an agent.

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 only 14%, so description must compensate. It adds meaning for 'size' with example '+10G' and for 'confirm' with 'confirm=True to execute', but other required parameters like disk, vmid, kind, node are not explained.

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?

Description clearly states it is a mutation tool to grow a guest disk (specific verb+resource). It provides an example format for size and distinguishes among sibling tools by focusing on disk resizing, which is unique.

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?

Explicitly states 'GROW ONLY' and that shrink is refused, giving when to use and not use. Also notes dry-run default and confirm flag, but does not mention alternative tools for disk operations.

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