ncloud_ncr_update_image

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

Annotations already declare idempotentHint=true and destructiveHint=false, indicating a safe, non-destructive operation. The description adds that only the description is updated, but does not disclose additional behaviors such as whether the registry must exist, whether the description overwrites or appends, or any confirmation response.

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 a single sentence that efficiently conveys the tool's purpose with no superfluous words. It is directly front-loaded and easy to parse.

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 tool's simplicity (update a single field), the description is largely complete. However, it could mention that it does not update other image attributes and that the return value (if any) is not documented, but this is acceptable as there is no output schema.

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 coverage is 100%, so the description neither adds nor detracts from parameter understanding. The description reinforces the purpose but does not elaborate on the format, constraints, or validation of parameters like 'description'.

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 the action 'Update' and the specific resource 'description of a container image in a registry'. It distinguishes from sibling NCR tools like ncloud_ncr_list_images, ncloud_ncr_get_image, and ncloud_ncr_delete_image by focusing solely on updating the description field.

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 does not provide explicit when-to-use or when-not-to-use guidance. Since this is the only update tool for container images, usage is implied, but the description lacks context about alternatives or prerequisites (e.g., that the image must already exist).

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