ncloud_sourcebuild_list_buckets

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

The description is read-only and consistent with the 'readOnlyHint' annotation, but provides no additional behavioral context such as response format or permissions. The annotation already covers the safety aspect.

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 8 words, front-loading the purpose. No redundancy or 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 read-only list operation with no parameters, the description explains the purpose and distinguishes from siblings. However, it lacks details about the return value (e.g., bucket names or attributes), which would be helpful given no output schema.

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?

There are zero parameters, so the description does not need to explain parameter semantics. The schema coverage is 100% trivially, and the description adds no parameter information, which is acceptable.

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 specifies the verb 'List', the resource 'Object Storage buckets', and the context 'available for SourceBuild artifact storage', distinguishing it from other 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 implicitly indicates when to use this tool (for SourceBuild artifact storage), but does not explicitly state when not to use it or mention alternatives like 'ncloud_list_buckets'.

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