vpc_create

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

No annotations are provided, so the description carries the disclosure burden. It does disclose defaulting behavior for v4_subnet and v4_subnet_mask and summarizes the return value. It does not address permissions, billing, idempotency, or whether this is the legacy path versus vpc_create_vpc2.

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 front-loaded with a clear one-liner and then organized into compact Args and Returns sections. It is not bloated, but the 'ctx' line is extraneous for a tool caller and prevents a perfect score.

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 description is enough to construct a basic call: required fields, optional subnet fields, defaults, and return summary are all present. It is incomplete as a selection aid because it never mentions the closely related vpc_create_vpc2 family, and no annotations or schema descriptions help fill that void.

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?

Input schema description coverage is 0%, and the description compensates thoroughly: every schema parameter is explained with an example or default, and optionality is clarified. The only minor blemish is the 'ctx' entry, which does not appear in the input 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 opening line 'Create a new VPC' uses a specific verb and resource, clearly identifying the action. It does not distinguish itself from the sibling vpc_create_vpc2, which also appears to create a VPC, so it stops short of the top score.

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 gives no guidance on when to use vpc_create versus vpc_create_vpc2, vpc_update, or any other sibling tool. An agent must infer selection from the tool name alone, and the overlap with vpc_create_vpc2 makes this a real gap.

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