ncloud_add_member_server_image_sharing

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

Annotations only declare destructiveHint=false, but the tool is still a mutation operation. The description does not disclose whether sharing is additive or replaces existing permissions, whether the operation is idempotent, or what happens if permissions already exist. It adds no behavioral context beyond the basic action.

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 that front-loads the core action and resource. There is no redundancy or filler; every word contributes to understanding.

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 mutation tool with no output schema and minimal annotations, the description is too sparse. It omits important contextual details such as whether the operation is additive, whether target accounts must exist, or any error conditions. The agent lacks sufficient information to predict side effects or verify success.

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%, with both parameters clearly documented in the schema. The description's phrase 'specified accounts' maps to targetLoginIdList but adds no additional semantic detail beyond what the schema already provides.

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 ('Add sharing permission'), the resource ('member server image'), and the target ('specified accounts'). It distinguishes itself from sibling tools like ncloud_add_server_image_sharing by explicitly naming 'member server image'.

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?

Usage context is implied by the action verb 'Add' - an agent can infer this is for granting sharing access. However, there is no explicit comparison with alternatives like ncloud_set_member_server_image_sharing or ncloud_remove_member_server_image_sharing, and no prerequisites or exclusions are mentioned.

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