cloud_insts_imgs_del

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

With no annotations, the description discloses the constraint about protected snapshots and details the resolution process for project and region identifiers. Lacks mention of return values or irreversibility, but is sufficient for a deletion 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 verbose, especially the 'Args:' section which duplicates schema information. The important resolution note is long but could be more succinct. Front-loading is adequate but not optimized.

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 no annotations, the description covers the core action and constraints. It does not explain return values or success indications, but for a simple delete operation, it is reasonably complete.

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?

Input schema has 0% description coverage. The description explains the resolution for project_id and region_id but only lists extra_headers, extra_query, extra_body, and timeout without adding meaning beyond the schema. Partially compensates for missing schema 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 'Delete a specific image' with a specific verb and resource. It distinguishes from sibling tools like cloud_insts_imgs_ls (list), cloud_insts_imgs_get (get), etc., by the action of deletion.

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?

Provides explicit guidance on resolving project_id and region_id, and notes that deletion is blocked if image is used by protected snapshots. Does not explicitly state when to use this tool over alternatives, but the context is helpful.

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