ncloud_list_postgresql_buckets

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

Annotations include readOnlyHint=true, which already communicates that this is a safe, read-only operation. The description adds the behavioral nuance that buckets are scoped to those available for Cloud DB for PostgreSQL, but does not disclose return format, pagination, or permissions. This is acceptable but minimal.

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?

A single succinct sentence with a parenthetical clarification. Every word contributes to the meaning, and the description is front-loaded with the primary verb and resource.

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?

This is a simple list operation with one optional parameter, no output schema, and a clear read-only annotation. The description covers the core purpose and scope effectively. It could mention response contents more explicitly, but given the tool's simplicity, it is sufficiently 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 one optional parameter, regionCode, with a complete description ("Region code (KR, KRS). Defaults to current region."), providing 100% schema coverage. The tool description adds no extra parameter context, so it offers no value beyond the schema.

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 available for Cloud DB for PostgreSQL), and the context (for backup export). This distinguishes it from sibling bucket-listing tools like ncloud_list_buckets and ncloud_list_mongodb_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 usage for PostgreSQL backup export but provides no explicit when-to-use guidance or alternatives. It neither excludes other uses nor contrasts with sibling tools, leaving the agent to infer appropriate invocation contexts.

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