ncloud_list_postgresql_backups

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

The annotation readOnlyHint=true already declares the read-only nature. The description adds only 'List backups for a Cloud DB for PostgreSQL instance,' which restates the function without disclosing additional behavior such as pagination, default limits, or what backup information is returned. No behavioral context is added beyond the annotations.

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 resource. It is concise, contains no unnecessary information, and is appropriately sized for a simple read operation.

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 tool with one parameter and no output schema, the description is minimal. It fails to specify what the returned backup list contains or how it differs from the sibling `ncloud_list_postgresql_backup_details`. The agent may not know whether this returns summaries or full details, but the parameter is self-explanatory and the operation is straightforward, making it minimally adequate.

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 required parameter `cloudPostgresqlInstanceNo` with description 'Cloud PostgreSQL instance number,' giving 100% schema coverage. The tool description does not add any further meaning about the parameter, such as format or how to obtain the instance number. Since schema coverage is high, the baseline of 3 applies.

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 identifies the resource as 'backups for a Cloud DB for PostgreSQL instance.' It clearly states the tool's function. However, it does not distinguish this tool from the sibling `ncloud_list_postgresql_backup_details`, which also relates to backups, so it lacks sibling differentiation.

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. There is no mention of prerequisites, exclusions, or references to sibling tools like `ncloud_list_postgresql_backup_details`. The agent is left to infer usage from the name alone.

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