aws_vpc

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

No annotations are provided, so the description carries full burden. 'Manage' implies both read and write operations, but the description doesn't disclose behavioral traits like authentication requirements, rate limits, destructive effects (e.g., deletion consequences), or response formats. For a tool with 9 parameters including potentially destructive actions like 'delete', this is a significant gap.

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, efficient sentence with no wasted words. It's appropriately sized for a high-level summary, though it lacks detail that might be needed given the tool's complexity. The structure is front-loaded but under-specified rather than concise.

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?

Given high complexity (9 parameters, nested objects, no output schema, and no annotations), the description is incomplete. It doesn't address the tool's scope, error conditions, or return values. For a multi-action tool (list/create/delete) with significant infrastructure implications, more context is needed to guide effective use.

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 0%, so the description must compensate. 'Manage AWS VPC networks' adds minimal meaning beyond the tool name. It doesn't explain what parameters like 'action', 'cidrBlock', 'dnsSupport', or 'subnets' do, how they interact, or which are required for specific actions. With 9 parameters and complex nested objects, the description fails to provide necessary context.

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 'Manage AWS VPC networks' states a general purpose (verb+resource) but is vague about what 'manage' entails. It doesn't distinguish this tool from sibling AWS tools like aws_ec2 or aws_cloudformation, which could also manage aspects of VPCs. The description lacks specificity about the actual operations available.

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 provides no guidance on when to use this tool versus alternatives. With multiple AWS-related sibling tools (e.g., aws_ec2, aws_cloudformation, terraform), there's no indication of this tool's specific role, prerequisites, or exclusions. Usage is implied only through the generic term 'manage'.

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