ncloud_get_postgresql_products

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

Annotations already declare readOnlyHint=true, and the description aligns with that read-only nature. It adds value by clarifying that the output is the list of server spec product codes and that the query depends on an image product code, which enriches the behavioral context beyond the bare annotation.

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 that is clear and directly states the tool's function. Every word earns its place with no fluff or repetition.

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?

Given the low complexity (2 params, 1 required), the readOnlyHint annotation, and full schema coverage, the description is sufficient for an agent to understand the tool's purpose and inputs. It lacks an explicit return-format description, but since it states it returns product codes and the schema covers parameters, it's reasonably complete for a simple listing operation.

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 description coverage is 100%, and both parameters have descriptions. The tool description adds little beyond the schema, only restating that the result is for a given image product code. The schema already names the source tool for the image product code, so the description provides minimal additional semantic value.

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 'List' and clearly identifies the resource: Cloud DB for PostgreSQL server spec product codes. It also specifies the required input (image product code), and the phrasing distinguishes it from sibling tools like ncloud_get_postgresql_image_products or ncloud_get_mysql_products.

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 when to use it: after obtaining an image product code from ncloud_get_postgresql_image_products. It doesn't explicitly mention alternatives or exclusions, but the 'for a given image product code' dependency provides clear context for when this tool is applicable.

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