resize_guest

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

The description discloses critical behaviors: disk resize is irreversible, and the confirm flag is required to execute (with a warning on first call). This goes beyond the bare mutation and alerts the user to side effects.

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 reasonably concise but includes some redundancy (e.g., listing parameters in prose and then again in arg list). Still, it is well-structured and not overly verbose.

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?

The description covers the essential context: what it does, prerequisites (at least one resource), and behavioral consequences. It is complete for a mutation tool without needing an output schema.

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?

Each parameter is explained with units (MB for memory), format (disk_size with units and examples), and defaults (disk default 'scsi0'). This adds meaning beyond the schema.

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 the tool's purpose: resizing CPU, memory, and/or disk of a VM or container. It is specific and distinguishes from other tools.

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?

It explicitly states that at least one resource must be provided, explains the effect on running guests (reboot required for CPU/memory) and that disk resize is immediate and irreversible. This provides clear when-to-use guidance.

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