ncloud_list_vpcs

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

The annotation readOnlyHint: true already indicates this is a safe read operation. The description adds the constraint 'in the current region', which is a useful scoping detail. No contradictions. It does not go into pagination or return format, but for a simple list operation with an annotation, this is adequate.

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: 'List all VPCs in the current region'. It is front-loaded with the action and resource, contains no fluff, and every word earns its place. Perfectly sized for the tool's simplicity.

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 read-only list tool with three optional self-documenting filters and no output schema, the description is nearly complete. It states the core behavior and scope. It could optionally mention that filters are supported, but the schema covers that. The presence of readOnlyHint and full schema coverage reduce the need for more detail.

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 description coverage is 100%, with all three parameters (vpcName, vpcNoList, vpcStatusCode) having clear descriptions. The tool description adds no additional parameter detail, but the schema already provides sufficient information. Baseline 3 is appropriate when the schema handles the heavy lifting.

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' with a clear resource 'VPCs' and a scope qualifier 'in the current region'. This clearly distinguishes it from sibling tools like get_vpc_detail which fetches a single VPC, and create_vpc/delete_vpc which are mutations. The purpose is unambiguous.

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 the tool's use case: when you need to list all VPCs in the current region. It does not explicitly mention alternatives or exclusions, such as using get_vpc_detail for a specific VPC. However, the verb 'list' and the resource name provide reasonable contextual guidance, so it's not completely absent.

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