cloud_update_image

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

No annotations are provided, so the description carries the full burden. It only states 'Update an image' and a constraint, but does not disclose behavioral traits such as whether updates are immediate, if they trigger cascading effects, or if they are reversible. This is insufficient for an update 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 concise with two sentences, no unnecessary words. The first sentence is a bit tautological with the tool name, but the second adds important context. Overall efficient, though front-loading the constraint might be beneficial.

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 presence of an output schema (not shown) and no annotations, the description is incomplete. It does not explain the return value or the post-update state. With 4 parameters and a requirement for image_id, the description lacks guidance on usage and behavior, making it barely adequate.

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 does not add any meaning to the parameters. It fails to explain what each parameter (image_id, description, type, labels) represents or how they affect the update, leaving the agent to rely solely on the schema, which lacks descriptions.

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 'Update an image' with a specific verb and resource, and adds a constraint that only user-created images (snapshots/backups) can be updated. This distinguishes it from sibling tools like cloud_create_server_image and cloud_delete_image, providing clear purpose and scope.

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 includes a constraint ('Only user-created images can be updated') which implies when not to use it (for system images). However, it does not explicitly state when to use it or provide alternatives, such as creating a new image via cloud_create_server_image. The guidance is minimal.

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