cloud_assign_floating_ip

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

With zero annotations, the description must fully disclose behavioral traits. It merely states 'Assign a floating IP to a server' without mentioning that this is a mutation, requires an existing floating IP, or what happens to any previous assignment. This is critically insufficient.

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 a single very short sentence, which is concise but lacks necessary detail. While no words are wasted, the saving in length comes at the expense of utility.

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?

Given the tool's action involves networking and state mutation, the description is woefully incomplete. It does not explain prerequisites, side effects, or return values, even though an output schema exists but is not leveraged in the description.

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 0% and the description adds no detail about the two required parameters (floating_ip_id, server_id). The agent cannot infer their semantics or relationships from the description alone.

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 (assign) and the entities (floating IP to a server). However, it does not distinguish from the sibling tool cloud_assign_primary_ip, which could cause confusion for an AI agent selecting between them.

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 guidance is provided on when to use this tool versus alternatives like cloud_assign_primary_ip or cloud_unassign_floating_ip. The agent receives no context for appropriate invocation.

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