cloud_rebuild_server

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

With no annotations, the description carries the full burden and clearly states the destructive nature ('destroys all data on the boot volume'). However, it lacks details on whether the operation requires the server to be off or how it affects attached storage.

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?

Single sentence, no unnecessary words, gets straight to the point.

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?

Description is minimal; it covers the destructive effect but omits potential prerequisites (power state, impact on attached volumes) and does not reference the output schema. An output schema exists but the description doesn't leverage it to explain return values.

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%, but the description mentions 'from an image', which relates to the 'image' parameter. The 'server_id' is self-explanatory. No additional parameter details are provided, making it adequate but not exceptional.

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 'Rebuild a server from an image' with a specific verb and resource, and adds critical context that it destroys the boot volume, distinguishing it from other server operations like create, change type, or reset.

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?

The description implies this is for reimaging a server but does not explicitly state when to use vs. alternatives like cloud_create_server or cloud_reset_server, nor does it mention prerequisites such as server power state.

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