ncloud_ses_get_snapshot_buckets

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

The annotation readOnlyHint=true is consistent with the description's 'Get ... list' action. The description adds that the list is filtered to buckets available for snapshot storage, but does not disclose additional behavior such as output format or permission requirements. Annotation coverage makes this acceptable.

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, front-loaded sentence with no redundant words. It efficiently conveys the action and purpose.

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 operation with one parameter, the description adequately conveys what the tool does. It does not specify the exact return structure, but the wording 'bucket list' implies a list of buckets. Given the low complexity and no output schema, this is sufficient.

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 has 100% coverage, with the single parameter 'serviceGroupInstanceNo' described as 'Cluster instance number'. The tool description does not add any extra parameter context, 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 clearly states the action ('Get') and resource ('Object Storage bucket list') with a specific purpose ('available for storing cluster snapshots'). This distinguishes it from sibling tools like ncloud_ses_get_import_buckets, which serve a different need.

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 implies the tool is for selecting buckets when setting up or managing cluster snapshots, providing clear context. It does not explicitly name alternatives or exclusions, but the purpose scoping makes the use case obvious.

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