cloud_insts_imgs_get

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

No annotations are provided, so the description carries full burden. It explains the necessary ID resolution logic for project and region, but does not disclose authentication requirements, rate limits, or whether the operation is read-only (implied by 'get'). It lacks information about the return format or side effects.

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 front-loaded with the purpose and structured with an Args list and note. The Args list is somewhat verbose for generic parameters like extra_headers, but overall it is organized and reasonably concise.

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 8 parameters, no annotations, and no output schema, the description covers the ID resolution logic but fails to document the required image_id parameter and does not explain what the tool returns (e.g., fields, structure). This leaves the agent with incomplete context.

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 explains most optional parameters (include_prices, extra_headers, etc.) and the required project_id and region_id in the Note. However, the required image_id parameter is not described at all, leaving a gap.

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 'Retrieve detailed information about a specific image,' which is a specific verb+resource. This distinguishes it from sibling tools like cloud_insts_imgs_ls (list images) and cloud_insts_imgs_del (delete images).

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 usage for getting a single image's details, but it does not explicitly provide when to use this tool vs alternatives like listing or deleting images. No exclusions or alternative tool names are mentioned.

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