ncloud_sourcebuild_list_buckets

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

Annotations declare readOnlyHint=true, and the description confirms this with 'List'. Additional context is added by specifying that the buckets are those 'available for SourceBuild artifact storage', indicating a filtered view. This is a useful behavioral detail beyond the 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 that immediately conveys the action, resource, and context. No unnecessary words or repetition.

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 and no output schema, the description is sufficient. It identifies the resource and its purpose. It could mention response format or pagination, but the simplicity of the tool reduces the need for that detail.

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 tool has zero parameters, so the baseline of 4 applies. The schema is empty and the description adds meaning by clarifying the purpose and scope of the listing, but there are no parameter semantics to expound upon.

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 ('List'), the resource ('Object Storage buckets'), and the specific context ('available for SourceBuild artifact storage'). This distinguishes it from other bucket-listing tools like ncloud_list_buckets and ncloud_sourcedeploy_get_objectstorage_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 phrase 'available for SourceBuild artifact storage' provides clear context for when this tool should be used (when dealing with SourceBuild). It does not explicitly exclude alternatives or name other tools, but the SourceBuild-specific scope is a strong signal.

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