ncloud_add_member_server_image_sharing

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

The description adds no behavioral context beyond the annotation destructiveHint: false. It does not disclose any side effects, required permissions, or response behavior. For a mutation tool, more transparency is expected.

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, efficient sentence with no unnecessary words. However, it could include more useful information without becoming verbose, such as indicating the effect of the sharing or that it applies to member server images only.

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 simplicity (2 params, non-destructive mutation), the description is adequate but leaves out differentiation from sibling tools and does not explain the return value. No output schema exists, so some expectation of result would be helpful.

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 both parameters already documented. The description repeats the parameter names without adding new meaning or clarifying formats, constraints, or relationships. 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 it adds sharing permission for a member server image to specified accounts, using a specific verb and resource. It distinguishes from sibling actions like removal and modification, as seen in sibling names such as ncloud_remove_member_server_image_sharing and ncloud_set_member_server_image_sharing.

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 like ncloud_add_server_image_sharing (for regular server images) or ncloud_set_member_server_image_sharing (to update existing sharing). No contexts or prerequisites are mentioned.

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