cloud_insts_resz

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

No annotations are provided, so the description carries full burden. It only mentions 'change flavor' but does not disclose behavioral traits like whether the instance is rebooted, if it's destructive, or if any states are required. This is a significant gap for a mutation tool.

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 structured with a purpose statement, an 'Args' list, and a 'Notes' paragraph. The 'Args' section is redundant as it only lists parameter names without descriptions. Could be more concise by integrating parameter explanations.

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 the complexity (8 parameters, 4 required, no output schema, no annotations), the description lacks crucial context: behavior during resize, prerequisites, error handling, and return value. It is insufficient for an agent to reliably invoke the tool.

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%, so the description must compensate. It adds meaning for project_id and region_id (explains resolution), but does not describe instance_id, flavor_id, or the extra_* parameters beyond their names. The notes add some value but are incomplete.

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 'Change flavor of the instance', which is a specific verb+resource. The tool name 'resz' implies resize, distinguishing it from siblings like cloud_insts_upd (update) or cloud_insts_act (action).

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 notes provide guidance on resolving project and region IDs (e.g., pass numeric, resolve names via other tools). However, it does not explicitly state when to use this tool over alternatives like cloud_insts_upd or prerequisites (e.g., instance must be stopped).

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