instance_delete_ipv4

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

With no annotations provided, the description must carry the full behavioral disclosure burden. It only states 'Delete an IPv4 address' and confirms a status message, but does not disclose side effects, permanence, whether the address is released back to the pool, or any constraints on when deletion is allowed. This is a significant gap for a destructive operation.

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 appropriately sized: a one-line purpose statement, a succinct Args section, and a Returns line. It is front-loaded with the core action and contains no filler or redundancy.

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?

For a simple two-parameter delete tool, the description covers the essential what, parameters, and return value. However, because it is destructive and has no annotations, the lack of usage context and behavioral caveats leaves meaningful gaps in understanding the full impact and appropriate invocation conditions.

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 is bare (0% coverage, just type strings), but the description adds meaningful semantics by explaining instance_id accepts an ID, label, or hostname with concrete examples, and clarifies ipv4 as the address to delete. This helps an agent format arguments correctly.

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 first sentence, 'Delete an IPv4 address from an instance,' clearly identifies the verb (delete) and resource (IPv4 address on an instance). It differentiates from sibling tools like instance_create_ipv4 and instance_list_ipv4 by stating the specific action without ambiguity.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites (e.g., whether the IP must be a secondary address or attached to the instance). The intended usage is only implied by the tool name and the action line.

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