ncloud_remove_member_server_image_sharing

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

The description adds behavioral context beyond annotations by explicitly warning 'DESTRUCTIVE' and specifying that confirm=true is required to execute. This complements the destructiveHint annotation and adds important operational detail.

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 a single sentence with a warning symbol, clear action, and critical instruction. Every word serves a purpose with no redundancy.

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 schema coverage and annotations, the description covers the core purpose and the key usage note. It does not mention idempotency or return behavior, but the annotations provide idempotentHint. The absence of output schema makes return info less critical.

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% with detailed descriptions for each parameter. The description only reiterates the confirm parameter's purpose but does not add new information about targetLoginIdList or memberServerImageInstanceNo beyond what is already 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 the action 'Remove sharing permission for a member server image', using specific verb and resource that aligns with the tool name and distinguishes it from sibling tools like add and set operations.

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 clear guidance on the confirm parameter ('Set confirm=true to execute'), which is essential for safe use. However, it does not explicitly differentiate when to use this tool versus similar tools like ncloud_remove_server_image_sharing, though the tool name itself implies the scope.

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