ncloud_remove_member_server_image_sharing

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

Annotations declare destructiveHint and idempotentHint. The description adds the confirm=true safeguard requirement and a strong 'DESTRUCTIVE' warning, going beyond the structured annotations. It does not detail post-conditions or reversibility, but the annotations already cover the destructive nature.

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 with a clear warning emoji and front-loaded destructive alert. Every word contributes: the action, the resource, and the execution requirement. No redundancy or filler.

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?

The schema covers all parameters, annotations cover destructive/idempotent behavior, and the description specifies the confirmation gate. For a focused permission removal tool, this is largely complete. It lacks mention of what happens after removal (e.g., immediate loss of access), but the destructive hint already signals consequences.

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 baseline is 3. The description does not add additional meaning to the parameters; it only repeats the confirm requirement already present in the schema. No extra context for targetLoginIdList or memberServerImageInstanceNo is provided.

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 states a specific action: 'Remove sharing permission for a member server image.' It includes the resource type ('member server image') and distinguishes from sibling tools like ncloud_remove_server_image_sharing by scoping to member images. The destructive warning and confirm requirement add clarity.

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 explicitly mention when to use this tool versus alternatives such as ncloud_add_member_server_image_sharing or ncloud_remove_server_image_sharing. It provides an operational guideline ('Set confirm=true to execute') but no selection guidance or exclusions.

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