cloud_delete_server

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

With no annotations, the description carries the full burden. It mentions irreversibility, which is critical for a destructive action, but fails to disclose other behaviors like required permissions, impact on attached resources, or error scenarios. The transparency is acceptable but incomplete.

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?

Two short sentences front-load the action and key consequence (irreversibility). No extraneous information; every word is necessary.

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?

Despite having an output schema (unknown content), the description lacks critical context for a destroy operation: what happens to floating IPs, volumes, networks; whether the server must be powered off; rate limits; error messages. This incompleteness could lead to incorrect or dangerous invocations.

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 0%, so the description should compensate by explaining the parameter server_id. It does not mention how to obtain it, its format, or any constraints. The description adds no value beyond the schema's type and requirement.

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 tool deletes/destroys a cloud server and emphasizes irreversibility, which distinguishes it from siblings like cloud_power_off_server or cloud_reboot_server. The verb 'Delete (destroy)' is specific and the resource 'cloud server' is unambiguous.

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 on when to use this tool versus alternatives (e.g., power off, reboot). The only hint is irreversibility, which implies caution but does not provide context such as prerequisites (e.g., server must be stopped) or post-effects (e.g., associated resources deletion).

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