ncloud_list_postgresql_buckets

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

The description adds no behavioral details beyond the readOnlyHint annotation. It does not mention authentication, rate limits, or what the operation affects. However, it does not contradict any annotations, so it is adequate.

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 sentence of 13 words. It is front-loaded with the verb and resource, and every word adds value. No extraneous 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 tool with one optional parameter and no output schema, the description is mostly complete. It specifies the context (PostgreSQL backup) and action. A minor improvement would be to mention the return type (list of bucket names), but it is sufficient.

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?

Schema coverage is 100% (regionCode described in schema). The description does not add extra meaning beyond the schema; it does not elaborate on the parameter's usage or format further.

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 and resource: 'List Object Storage buckets available for Cloud DB for PostgreSQL (for backup export)'. It clearly distinguishes from sibling tools like generic bucket listing and other DB-specific bucket lists by including the database type and purpose.

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 does not explicitly state when to use this tool versus alternatives like ncloud_list_buckets or ncloud_list_mssql_buckets. No when-not or exclusion guidance is provided.

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