unassign_ip

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true; the description merely restates the DELETE verb already implied by those hints. It says nothing about consequences — whether the IP is released back to the pool, whether the VIP must currently be assigned, or what authorization is needed. The 'to'/'from' wording even muddies direction.

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?

Two short sentences plus the endpoint reference, but the second sentence largely repeats the first ('Unassign a VIP to a VPS/VDS/Bare Metal' vs. 'Unassign a VIP from an VPS/VDS/Bare Metal using the machine id'). Front-loaded and not bloated, but redundant rather than additive.

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?

Safety profile is covered by annotations and all parameters are documented, but for a destructive unassign operation the description leaves the outcome (what happens to the IP/VIP pairing) and preconditions unstated, and there is no output schema to explain the response.

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 the schema already documents ip, resourceId, resourceType (with its enum), and x-trace-id. The description adds only the phrase 'using the machine id' to clarify resourceId, which is marginal added meaning — baseline 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?

Names a specific verb (unassign), resource (VIP), and target types (VPS/VDS/Bare Metal), plus the underlying DELETE endpoint. An agent can tell it apart from assign_ip by the verb, but the description never names that sibling explicitly and contains a grammar slip ('Unassign a VIP to a VPS').

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 statement of when to use this vs. assign_ip or the other VIP tools, no prerequisites (must the VIP already be assigned?), and no failure conditions. Only 'using the machine id' hints at the required identity.

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