ncloud_add_server_image_sharing

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

The description adds minimal behavioral detail beyond 'Add sharing permission'. It does not explain whether permissions are additive or replace existing, or if there are any side effects. The destructiveHint=false annotation indicates it is non-destructive, but the description carries the burden since annotations are sparse. It is adequate but could be more explicit.

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, concise sentence with 12 words. It is front-loaded and contains no unnecessary information, earning its place fully.

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?

For a tool with two simple parameters, full schema coverage, and no output schema, the description is largely sufficient. It could benefit from clarifying what happens to existing permissions, but overall it provides enough context to invoke the tool correctly.

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%, so the description does not need to expand on parameters. It provides no additional meaning beyond the schema descriptions for serverImageNo and targetLoginIdList. Baseline score of 3 is appropriate.

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 verb 'Add', the resource 'server image', the action 'sharing permission', and the target 'specified accounts'. It distinguishes itself from sibling tools like remove and member server image sharing by focusing on adding permission to regular server images.

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 versus alternatives (e.g., remove_server_image_sharing or add_member_server_image_sharing). It does not mention prerequisites, such as the server image existing or the accounts being valid, nor does it clarify that this complements the remove operation.

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