ncloud_get_snapshot_detail

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds 'detailed information,' which implies a response with snapshot details, but it does not disclose additional behavioral traits such as response format, required permissions, or error conditions. Given the annotation coverage, this is adequate but minimal.

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 action and resource. No extraneous words or repetitions; every word earns its place.

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?

This is a simple one-parameter, read-only detail retrieval tool. The description adequately conveys the core purpose. While there is no output schema, the phrase 'detailed information' hints at the return type. For such a straightforward tool, the description is sufficiently complete, though it could specify what details are returned.

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?

The input schema provides 100% coverage with a clear description for the single parameter ('Block storage snapshot instance number to query'). The tool description adds no additional meaning beyond the schema, so the 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 uses a specific verb ('Get') and clearly identifies the resource ('detailed information about a specific block storage snapshot instance'). It distinguishes this tool from sibling tools like ncloud_list_snapshots (listing) and ncloud_create_snapshot (creation).

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: use this when you need details of a specific snapshot instance. However, there is no explicit mention of when to use this over alternatives (e.g., when you already have the snapshot instance number vs. needing to list snapshots first). No exclusions or alternative tool references are provided.

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