ncloud_get_postgresql_target_subnets

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

Annotations already declare readOnlyHint=true, and the description's 'List subnets' is consistent. The description adds no additional behavioral details (e.g., authentication, rate limits, output format). No contradiction with 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 concise sentence that conveys the core purpose without extraneous words. However, it lacks structural elements like bullet points or separate use-case descriptions.

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?

Without an output schema, the description does not specify the format or details of the returned subnets. Given the simplicity of the tool, it is adequate but incomplete. Sibling tools with similar patterns exist, but the agent would benefit from more context.

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 covers both parameters with 100% description coverage. The description reinforces the need for a specific PostgreSQL instance (cloudPostgresqlInstanceNo) but does not explain the optional regionCode beyond the schema. Minimal added 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 clearly specifies the action ('List subnets'), the resource ('for Cloud DB for PostgreSQL instance creation'), and the scope ('within a specific PostgreSQL instance'). However, it does not explicitly differentiate from sibling tools like ncloud_get_mysql_target_subnets, though the name implies the database type.

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 usage context ('for instance creation'), but provides no explicit guidance on when to use this tool versus alternatives such as ncloud_get_postgresql_target_vpcs or subnet listing tools for other databases. No exclusions or prerequisites are mentioned.

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