ncloud_list_export_buckets

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

The annotation readOnlyHint=true already informs the agent that the tool is read-only. The description adds that it lists buckets available for log export, but does not disclose other behavioral traits such as pagination, response structure, or any defaults. The description adds modest value beyond annotations.

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 of 13 words that immediately conveys the tool's purpose. It is front-loaded and contains no unnecessary information.

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 list tool with one optional parameter and no output schema, the description is mostly complete. It identifies the subject (export target buckets) and context (Cloud Log Analytics). Minor gaps include no mention of pagination or typical response structure, but these are not critical for a straightforward listing operation.

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% with the parameter 'regionCode' already documented clearly. The description does not add additional semantic meaning or constraints beyond what the schema provides. Since the schema already does the heavy lifting, a 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 verb 'List', the resource 'Object Storage buckets', and narrows the scope to those 'available as log export targets in Cloud Log Analytics'. This distinguishes it from general bucket listings (e.g., ncloud_list_buckets) and provides a specific purpose.

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 implicitly guides usage by specifying the context (log export targets), but it does not explicitly state when to use this tool versus alternatives like ncloud_list_mssql_buckets or ncloud_list_cache_buckets. The clarity of the purpose partially compensates for the lack of explicit when-to-use advice.

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