iaas_resize_machine

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, openWorld=true, so the safety profile is partly covered. But the description adds nothing beyond that: it doesn't mention whether the operation is asynchronous, whether the machine must be powered off, or what happens on failure — all critical for a non-idempotent mutation.

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?

Very short, but the middle line 'Second day resize operation for machine' is redundant and unclear rather than informative, and the endpoint line is metadata rather than guidance. Front-loaded purpose is fine but one of three lines doesn't earn 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?

For a mutation tool with no output schema and no description of async behavior, power-state prerequisites, or return/error semantics, the description is too thin. It relies entirely on annotations and schema to convey everything an agent needs.

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 every parameter including rebootMachine's vSphere hot-add caveat is documented in the schema itself. The description adds no parameter meaning beyond the schema, so the baseline of 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 and resource ('resize operation for machine'), so an agent knows it changes machine compute characteristics. However, 'Second day resize operation' is confusing/unclear filler and the description doesn't distinguish it from siblings like iaas_update_machine or iaas_resize_block_device.

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?

No guidance on when to use this versus iaas_update_machine, iaas_resize_block_device, or the power operations. No prerequisites such as machine power state requirements or that resize may require a reboot are given.

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