ncloud_sourcedeploy_get_objectstorage_buckets

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

The annotation readOnlyHint: true already signals that this is a safe read operation, and the description's 'Get the list' is consistent with that. Beyond the annotation, the description adds minimal behavioral context, merely restating the retrieval purpose with a stage-configuration qualifier. No additional behavioral traits (pagination, sorting, permissions, or response details) are disclosed.

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 that immediately states the action and resource. Every word contributes meaningful context, with no filler or redundancy.

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 (no parameters, no output schema, read-only annotation), the description adequately conveys the purpose and scope. It tells the agent what will be returned ('list of available Object Storage buckets') and the context ('SourceDeploy stage configuration'), which is sufficient for a parameterless listing tool. However, it does not describe the format or contents of the returned bucket list, which would be useful but not essential here.

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 takes zero parameters, and the input schema confirms this with an empty properties object. With no parameters to explain, the description does not need to provide parameter semantics; the baseline of 4 for zero-parameter tools 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 uses a specific verb ('Get') and a clear resource ('list of available Object Storage buckets') with a scoping qualifier ('for SourceDeploy stage configuration'). This distinguishes it from general bucket listing tools like ncloud_list_buckets and from object-level tools like ncloud_sourcedeploy_get_objectstorage_objects, though it does not explicitly name these siblings.

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 'for SourceDeploy stage configuration' implies a use case, but the description offers no explicit guidance on when to choose this tool over alternatives (e.g., ncloud_list_buckets or ncloud_sourcedeploy_get_objectstorage_objects). It also does not mention exclusions or preconditions.

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