cloud_create_server

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

With no annotations, the description carries full burden but only states 'Create a cloud server.' It does not disclose whether creation is immediate, idempotent, or requires specific permissions. No behavioral traits beyond the generic action are revealed.

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 very short and to the point, which is good for conciseness. However, it sacrifices necessary detail; it could be restructured to include core parameter guidance without adding much length.

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 high parameter count (15), lack of schema descriptions, and no annotations, the description is incomplete. It does not address how to set up ssh_keys, volumes, networks, etc., nor explain the output. The agent lacks sufficient context to use the tool reliably.

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%, so the description must compensate. It only adds examples for 'server_type' and 'image', leaving 13 other parameters unexplained. This is insufficient for an agent to correctly populate all fields.

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 it creates a cloud server and provides examples for two key parameters, which helps the agent understand the basic action. However, it does not differentiate from sibling tools like cloud_create_server_image or cloud_change_server_type, so the purpose is clear but not fully distinctive.

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, nor any prerequisites or when not to use it. The description lacks any usage context, leaving the agent to infer from the name alone.

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