ncloud_list_postgresql_instances

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

Annotations already declare readOnlyHint=true, so the description does not need to restate that. It adds the 'current region' scoping, which is useful. However, it does not disclose behavior such as pagination limits, default page size, or what fields are returned in the response (no output schema is provided).

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 (11 words) that is front-loaded with the verb and resource. Every word contributes, with no fluff or repetition of schema 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?

The tool has 4 optional parameters and no output schema, but the description only covers purpose and region. It does not mention pagination parameters, filter options, or the shape of the returned list. For a list tool this is minimally adequate but leaves gaps for an agent to discover via schema and API knowledge.

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 description coverage is 100%, so the baseline is 3. The description does not add meaning beyond the schema; it says 'all' which may imply no filtering, but the optional filter parameters are not mentioned. It neither contradicts nor enriches 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'), resource ('Cloud DB for PostgreSQL instances'), and scope ('in the current region'). This distinguishes it from sibling tools like ncloud_get_postgresql_instance_detail (single instance detail) and ncloud_create_postgresql_instance (creation).

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 use when you need all PostgreSQL instances in the current region, but provides no explicit guidance on when to choose this over alternatives, nor does it mention pagination or filtering capabilities. The availability of get_postgresql_instance_detail suggests a distinction, but it is not stated.

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