ibmcloud_cr_image_rm

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the deletion action but does not mention irreversibility, whether the 'force' flag is required or affects behavior, or any side effects on related tags. This is a significant gap for a destructive 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 a single, clear sentence that immediately conveys the purpose. It is appropriately sized for a simple operation and uses no unnecessary words.

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?

Despite being a simple 2-parameter tool, the lack of annotations and minimal description leaves out critical context for a destructive action. The absence of usage guidelines and behavioral transparency makes it incomplete for an agent deciding whether and how to invoke this tool.

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?

The input schema already provides complete descriptions for both parameters ('image' and 'force'), so schema coverage is high (100%). The description adds no additional parameter semantics beyond what the schema offers, thus the baseline of 3 applies.

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 ('Remove') and the resource ('a container image'), which is specific and distinct from sibling tools like ibmcloud_cr_images (list images) and ibmcloud_cr_namespace_add. It follows the pattern of a destructive operation on a single resource.

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 provides no guidance on when to use this tool, prerequisites, or exclusions. It does not mention alternatives (e.g., ibmcloud_cr_images for listing before deletion) or any conditions for safe deletion. The usage context is only implied by the tool name.

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