cloud_delete_primary_ip

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

With no annotations, the description carries the full burden. It states the action is a deletion but does not disclose irreversibility, error scenarios (e.g., failure if still assigned), or side effects. More detail on the destructive nature and constraints would improve transparency.

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 two short sentences with no extraneous information. It front-loads the action and immediately follows with the key precondition. Every word earns its place.

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 one-parameter deletion tool, the description covers the action and a critical precondition. However, it lacks details about the return value (despite an output schema existing) and error handling. The presence of an output schema partially mitigates this, but the description could be more complete.

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 schema description coverage is 0%, so the description must compensate. The description provides no additional meaning for the parameter 'primary_ip_id' beyond its name; it doesn't specify format, source, or validation requirements. This is insufficient.

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 ('Delete a primary IP') with a specific verb and resource. It distinguishes from siblings like cloud_create_primary_ip, cloud_unassign_primary_ip, and cloud_update_primary_ip, which have different purposes.

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 includes a precondition ('Must be unassigned first'), which indirectly suggests using cloud_unassign_primary_ip if the IP is still assigned. However, it does not explicitly state when to choose this tool over alternatives or provide context for typical use cases.

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