set_vm_ip

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only mentions the guest agent requirement but does not explain that this modifies the VM's network configuration, potential side effects, reversibility, or required permissions. 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 a single, concise sentence that immediately states the action and the key prerequisite. It is front-loaded and free of unnecessary words, making it easy to parse.

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 tool has six parameters, no output schema, and no annotations, yet the description only provides a minimal statement of purpose and one prerequisite. It lacks information on behavior, return values, error conditions, or post-conditions, making the description insufficient for an AI agent to fully anticipate the tool's effects.

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 input schema provides descriptions for all six parameters, achieving 100% coverage. The description does not add extra detail beyond the schema, but it correctly points to the tool's purpose. Baseline 3 is appropriate because the schema handles parameter documentation.

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 action (Set IP address) and the resource (a VM), making the tool's purpose easily identifiable. It distinguishes itself from sibling tools like set_vm_hostname by focusing specifically on IP configuration. However, it does not explicitly mention the interface or network scope, which would make it fully unambiguous.

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 description notes 'requires guest agent', which is a prerequisite for using the tool, providing useful context on when this tool is applicable. It does not mention when to use this tool versus alternatives or explicitly exclude other scenarios, so guidance is limited but not absent.

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