ncloud_ses_get_snapshot_buckets

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

Beyond the readOnlyHint annotation, the description discloses a critical prerequisite (must run set_snapshot_api_key first) and the specific error code (10115) when that is violated. It also notes the behavioral difference from the import counterpart, adding significant context for agent decision-making.

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 two sentences with no waste. The first sentence states the core purpose, and the second adds the prerequisite and alternative. Information is front-loaded and every sentence 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?

For a simple read-only list tool with one parameter, the description covers purpose, prerequisite, alternative, and error condition. It does not explicitly describe the return format (e.g., list of bucket names), though it is implied by 'bucket list'. Given no output schema, a slightly richer response description could help, but it is adequate as is.

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% — the only parameter, serviceGroupInstanceNo, is already described as 'Cluster instance number'. The description adds no additional parameter meaning, so baseline 3 applies.

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 states a specific verb ('Get'), resource ('Object Storage bucket list'), and scope ('for storing cluster snapshots'). It explicitly names the sibling tool ncloud_ses_get_import_buckets and differentiates by the key requirement, so an agent can distinguish it without opening the schema.

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?

It gives explicit when-to-use guidance: requires ncloud_ses_set_snapshot_api_key to have been run first, otherwise fails with 10115. It also names the alternative (ncloud_ses_get_import_buckets) and clarifies that one does not need the key, providing clear selection logic.

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