ncloud_list_snapshots

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds no additional behavioral context, such as pagination behavior, rate limits, or any potential side effects. It merely restates the tool's function without disclosing any implicit behaviors.

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 sentence that conveys the essential purpose without superfluous words. It earns its place by being clear and direct, though it could provide more detail without sacrificing conciseness.

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 that there is no output schema, the description does not clarify the return format (e.g., list of snapshot objects, pagination metadata). It also omits how parameters like pageNo/pageSize are used together. For a listing tool, these details are important for the agent to understand the response structure and use the tool effectively.

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 baseline is 3. The description does not add meaning beyond what the schema provides; it doesn't explain how parameters like blockStorageSnapshotInstanceNoList filter results or that pageNo/pageSize control pagination. However, the schema itself covers these details sufficiently.

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 'List all block storage snapshot instances', specifying the action (list) and resource (block storage snapshot instances). It implicitly distinguishes from sibling tools like ncloud_get_snapshot_detail (single snapshot) and ncloud_create_snapshot, as listing is a different operation.

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_get_snapshot_detail. It does not mention filtering, pagination, or any context for use, leaving the agent to infer usage solely from the name and schema.

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