ncloud_ncr_update_image

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

The annotations already declare idempotentHint=true and destructiveHint=false. The description adds no additional behavioral context, such as whether updating one field affects the other, overwrite semantics, or any side effects. It simply restates the action without enriching beyond the annotations.

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, clear sentence with no unnecessary words. It is appropriately sized for a simple update operation.

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?

With full schema coverage and annotations, the description covers the core purpose but leaves gaps: it does not clarify the relationship between the optional description and fullDescription fields, nor the expected response or behavior when no optional fields are supplied. No output schema is present, so return semantics are entirely unaddressed.

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 100% for all parameters, so the baseline is 3. The description does not add any meaning beyond the schema's parameter descriptions; it only mentions 'description' ambiguously without clarifying the separate description and fullDescription fields.

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), the resource (container image description), and the location (registry). It distinguishes this tool from siblings like ncloud_ncr_delete_image or ncloud_ncr_get_image by specifying exactly what is updated.

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?

No guidance is provided on when to use this tool versus alternatives or on prerequisites. It does not mention that description and fullDescription are optional or what happens if both are omitted. The description lacks context about the update scenario.

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