ncloud_get_cache_target_vpcs

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

The description does not add behavioral context beyond the readOnlyHint annotation. It does not disclose permissions, rate limits, or pagination. However, it does not contradict the annotation indicating a read-only operation.

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 efficiently communicates the tool's purpose with no redundant or unnecessary words.

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 no output schema, and the description provides minimal context. It does not explain what kind of VPCs are returned (e.g., all VPCs in the account vs. those compatible with Cache) or how the optional region code affects results. This is adequate for a simple list operation but leaves some ambiguity.

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 already describes the only parameter (regionCode) with examples. The description adds no additional semantic meaning beyond what is in 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 tool lists VPCs available for Cloud DB for Cache, using a specific verb ('List') and resource. It distinguishes from the general 'list_vpcs' sibling by specifying the database 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?

While the description implies use for Cache-related VPC selection, it does not explicitly mention when to use this tool over alternatives like 'list_vpcs' or 'get_mysql_target_vpcs'. However, the tool name and description provide sufficient context for an AI agent to infer the correct use case.

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