ncloud_create_snapshot

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

Annotations provide 'destructiveHint: false', which the description does not contradict. However, the description adds minimal behavioral context beyond the dryRun feature. It does not disclose whether creation is synchronous, billing impact, or effect on source volume. With annotations covering only destructiveness, more detail would be beneficial.

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—two sentences with no filler. Every word serves a purpose. It is well-structured with a clear action and a helpful hint.

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 description does not explain the return value (e.g., snapshot ID or status) despite lacking an output schema. With 4 parameters (1 required) and no output schema, the description should at least mention what the agent can expect after creation. The dryRun hint partially compensates, but overall completeness is low.

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%—all 4 parameters are documented in the schema. The description adds value by highlighting 'dryRun=true' for preview, but does not add further meaning beyond the schema for other parameters. Baseline 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 action ('Create a snapshot') and the resource ('from a block storage instance'). It distinguishes from sibling tools like 'ncloud_list_snapshots' and 'ncloud_delete_snapshots' by using a specific verb and resource.

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 mentions the 'dryRun=true' option but provides no guidance on when to use this tool vs. alternatives like 'ncloud_create_nas_snapshot' or 'ncloud_create_server_image_from_snapshot'. No explicit when-to-use, when-not-to-use, or prerequisites.

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