ncloud_list_postgresql_databases

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

The description's 'List' aligns with the annotation 'readOnlyHint: true', but it adds no additional behavioral information beyond what the annotation already provides. It does not disclose whether the operation is instantaneous, requires specific permissions, or if there are limits on the number of databases returned. With annotations covering the safety aspect, a score of 3 is appropriate.

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 clearly states the tool's function. It is front-loaded with the action and resource, with no extraneous words.

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 parameter, the description is nearly complete. However, it does not mention what is returned (e.g., list of database names) or if there are pagination limits. Given the lack of an output schema, a brief note about the return type would be beneficial, but the core context 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% (one parameter fully described). The description does not add semantic meaning beyond the schema's 'Cloud PostgreSQL instance number'. It could clarify the format or source of this instance number, but the schema alone is sufficient for basic understanding.

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 'List databases in a Cloud DB for PostgreSQL instance' clearly specifies the action (list), resource (databases), and service (Cloud DB for PostgreSQL instance). It distinguishes this tool from sibling tools like 'ncloud_list_postgresql_backups' or 'ncloud_list_postgresql_users' by naming the resource type. The purpose is immediately understandable.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or suggest other tools for different needs (e.g., filtering, other PostgreSQL operations). The agent must infer usage context solely from the tool name and schema.

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