ncloud_ncr_delete_image

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds a warning emoji and the confirm requirement, but does not disclose additional important details such as whether deletion is immediate, irreversible, or affects associated tags. Minimal value added beyond 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 extremely concise, consisting of two short sentences with a prominent warning emoji. No filler or redundant information.

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 destructive nature and the presence of annotations and a full schema, the description provides the minimum necessary context. However, it lacks details on irreversibility or cascading effects, which could be valuable for an AI agent.

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%, so the schema already documents each parameter. The description clarifies the confirm parameter's role ('Must be true to actually execute'), adding some meaning, but does not elaborate on imageName or registryName beyond what's in the schema.

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 a specific verb ('delete') and resource ('container image'), making it distinct from sibling tools like ncloud_ncr_delete_registry (delete registry) and ncloud_ncr_delete_tag (delete tag).

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 only instructs to set confirm=true to execute, but provides no guidance on when to use this tool versus alternative deletion tools (e.g., delete tag vs delete registry). No use-case distinction is made.

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