ncloud_get_mysql_target_vpcs

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

Annotations already declare readOnlyHint=true, and the description is consistent ('List'). It adds meaningful context beyond annotations by specifying these are VPCs specifically available for MySQL instance creation, implying a filtered subset rather than all VPCs. No contradiction.

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 directly states the tool's purpose with no extraneous information. It is front-loaded with the verb and resource, making it instantly scannable.

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 list tool with one optional parameter and no output schema, the description adequately explains what it returns. It does not detail the response format or pagination, but that is not critical for this low-complexity operation. The sibling tool context reinforces its role in the MySQL instance creation workflow.

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 provides 100% coverage of the only parameter, regionCode, including its meaning and default behavior. The description adds no additional parameter details, which is acceptable since the schema already carries the full semantic load.

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 resource ('VPCs available for Cloud DB for MySQL instance creation'), clearly distinguishing it from generic VPC listing tools and from target-VPC tools for other database services. It states exactly what the tool returns and in what context.

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 clearly implies the tool should be used when creating a Cloud DB for MySQL instance and needing to know which VPCs are eligible. It does not explicitly mention alternatives like ncloud_list_vpcs or sibling tools for other databases, but the context is strong enough for an agent to infer when to use it.

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