cloud_list_floating_ips

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

With no annotations, the description partially discloses behavior: 'Read only, free' indicates safety and cost, and 'Compact by default' hints at output format. However, it omits details like filtering behavior, error cases, or pagination, which are important for a list 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 extremely concise with three short sentences. The first sentence efficiently states the purpose, and the following two add value. No wasted words; every sentence 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?

Given no output schema and 3 parameters (including nested object), the description is too minimal. It does not explain what floating IPs are, how query filtering works, or what the default vs verbose output contains. This lack of completeness may confuse an agent without additional context.

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 100%, so the schema already documents all 3 parameters. The description adds no additional meaning beyond what the schema provides (e.g., 'Compact by default' loosely links to verbose parameter but is not precise). Baseline of 3 is appropriate.

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 'List floating IPs' with a specific verb and resource. The name itself distinguishes it from sibling list tools targeting different resources (e.g., cloud_list_primary_ips, robot_list_ips). However, it does not explicitly differentiate from these siblings.

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. The description mentions 'Read only, free' but does not specify scenarios or prerequisites. Sibling tools exist for other IP types but no decision support is given.

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