scale_vmss

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

No annotations are provided, and the description does not disclose behavioral traits beyond 'Scale'. It does not mention whether the operation is destructive, asynchronous, requires permissions, or returns a result. Given the presence of an output schema, some description of what is returned would be helpful.

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 very concise with a single opening sentence followed by a clear list of arguments. Every word is functional, and it is front-loaded with the main action.

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 lack of annotations and the presence of an output schema, the description is incomplete. It does not explain the scaling behavior (e.g., manual vs. automatic), what happens during scaling, or what the tool returns. For a tool with three required parameters, more context would improve usability.

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?

The description adds some meaning beyond the schema by stating 'Resource group name', 'VM Scale Set name', and 'Target instance count (0+)', which clarifies the capacity parameter's valid range. However, it does not provide examples or further constraints.

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 scales a Virtual Machine Scale Set, which is a specific action. It lists the required resources (resource group, VMSS name, capacity). Among siblings, no other tool mentions 'scale', so it is distinguishable, though not explicitly.

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 is provided on when to use this tool versus alternatives (e.g., for individual VM operations vs. scaling the entire set). There is no mention of prerequisites or context like the VMSS needing to exist.

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