ncloud_list_export_buckets

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

The readOnlyHint annotation is consistent with the 'List' operation, and the description does not contradict it. However, it adds little behavioral context beyond the annotation, such as return format or pagination. For a simple list operation, this is adequate but not exceptional.

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, focused sentence that immediately states the action and resource. It contains no unnecessary information or redundancy, making it highly concise and effectively front-loaded.

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 the tool's simplicity (one optional parameter, read-only, no output schema), the description provides sufficient context for an agent to understand its purpose. It could mention expected return values, but for a basic list operation used in a specific context, it is mostly complete.

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 regionCode parameter explicitly described as 'Region code (default kr)'. The description does not need to add parameter details, and the schema fully documents the only parameter, so 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 identifies the action (List), the resource (Object Storage buckets), and the specific context (available as log export targets in Cloud Log Analytics). This distinguishes it from general bucket listing tools like ncloud_list_buckets.

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 finding buckets that can be used as log export targets, but it does not explicitly state when to use it versus alternatives or provide exclusions. The context is clear enough to infer usage, but no direct guidance on alternatives is given.

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