remove_ip_from_vps

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

Beyond the destructiveHint=true annotation, the description discloses that the operation is irreversible and that confirm=true is mandatory. It also clarifies the release-vs-detach semantic, which is important behavioral context for an agent selecting the 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?

Three short sentences with no filler: action, consequence, and alternative all front-loaded. Every sentence adds necessary information.

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 description plus destructiveHint and readOnlyHint=false gives an agent enough to decide and invoke safely, including the mandatory confirm flag. It does not distinguish from release_ip or describe the response, but there is no output schema and detach_ip covers the main confusion, so these are minor gaps.

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?

With 0% schema description coverage, the description must compensate. It adds the key parameter fact ('requires confirm=true') for the confirm field, while vps_id and ip_addr are adequately self-describing from their names and the tool name.

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 names a precise action ('Permanently remove (release) an IP address') and a precise resource ('from this VPS'). It explicitly contrasts itself with detach_ip, so an agent can distinguish it from the closest sibling without inspecting schemas.

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?

It gives an explicit precondition ('requires confirm=true') and names the correct alternative when detachment without release is desired ('To detach without releasing it, see detach_ip instead'). This is direct when-to-use guidance.

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