ncloud_list_postgresql_databases

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

The annotation readOnlyHint=true already signals a safe read operation, and the description's 'List databases' is consistent with that. No additional behavioral details like pagination, error conditions, or return format are provided, but given the annotation coverage the description meets the minimum viable standard.

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, front-loaded with the verb, and contains no unnecessary words or repetition. It is maximally concise while conveying the essential purpose.

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 one required parameter and a clear annotation, the description adequately communicates the tool's purpose. It doesn't describe the response format, but that is not critical given the simplicity and the presence of the readOnlyHint annotation.

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 schema covers the single parameter with a description ('Cloud PostgreSQL instance number'), and the tool description ties the parameter to the action ('in a Cloud DB for PostgreSQL instance') but does not add new semantic detail beyond what the schema already provides. Baseline applies due to 100% schema coverage.

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 the specific verb 'List' and clearly specifies the resource: 'databases in a Cloud DB for PostgreSQL instance'. This clearly differentiates it from sibling tools like ncloud_list_postgresql_instances and ncloud_list_postgresql_users.

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 the tool is for listing databases within a specific PostgreSQL instance, but it does not explicitly state when to use this over alternative list tools or provide any exclusions. The usage context is inferred from the resource type rather than being explicitly stated.

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