ncloud_get_cache_target_subnets

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

Annotations declare readOnlyHint: true, so the agent knows this is a read-only operation. The description adds that the listing is 'within a specific instance', but no further behavioral details (e.g., what happens if instance is invalid, rate limits, or result format). The description adds some value beyond annotations but not substantial.

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 succinctly conveys the tool's purpose with no unnecessary words or fluff. It is appropriately front-loaded.

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 two parameters and no output schema, the description is minimally adequate. It explains what is listed and the scope, but could be improved by hinting at the output format (e.g., list of subnet IDs) or any filtering behavior.

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 coverage is 100% with parameter descriptions for regionCode and cloudCacheInstanceNo. The description does not add any additional meaning beyond what the schema already provides, so baseline score 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 clearly states the action (List) and the resource (subnets available for Cloud DB for Cache within a specific instance). It distinguishes from sibling tools like ncloud_get_cache_target_vpcs (which lists VPCs) and ncloud_list_cache_instances (which lists instances).

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 does not provide when to use this tool versus alternatives, nor does it mention any prerequisites or restrictions. It simply states what the tool does without guiding the agent on decision-making.

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