Delete a floating IP

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

With no annotations, the description carries the full burden and does a good job: it discloses that the operation is destructive, that it is free of charge, that confirmation is mandatory, and that a dependent state (assigned) blocks it. It omits nothing critical for a delete, though it doesn't mention reversibility or auth requirements.

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, front-loaded with the core action, then cost/destructiveness, then the prerequisite. The stray 'Note. an assigned IP' punctuation is slightly awkward but costs no meaning.

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 two-parameter destructive tool with no annotations and no output schema, the description covers destruction, cost, confirmation requirement, and the unassign dependency — everything an agent needs to call it correctly. Only minor gaps (auth/scope) remain.

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 coverage is only 50% (only 'id' is documented). The description compensates by explaining the undocumented 'confirm' parameter ('requires confirm true'), which the schema leaves as a bare boolean. The 'id' parameter needs no further explanation than the schema already gives.

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?

States a specific verb and resource ('Delete a floating IP') that clearly distinguishes it from the many list_* and create_* siblings. It does not name the closely related cloud_unassign_floating_ip or cloud_create_floating_ip directly, but the prerequisite note implicitly routes to unassign.

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?

Gives an explicit precondition ('an assigned IP must be unassigned first') and a required calling condition ('requires confirm true'). It lacks an explicit alternative-tool pointer, but the when-to-use context is clear from the prerequisite.

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