AWS MCP Server

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

No annotations provided, so description carries full burden. It implies read-only access via 'describe' but does not confirm safety, disclose pagination behavior, rate limits, error conditions (e.g., invalid VPC IDs), or the structure/contents of returned data.

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?

Extremely brief (4 words) and front-loaded. While not verbose, it is under-specified rather than efficiently concise—it fails to leverage the available space to add value beyond the function name.

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 zero annotations, no output schema, and the complexity of AWS VPC relationships, the description is inadequate. It should clarify this maps to AWS DescribeVpcs API, mention pagination for large result sets, and explain how it relates to the broader VPC tool family.

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 has 100% description coverage, establishing baseline of 3. The description does not mention parameters or add context beyond what the schema already provides (e.g., explaining region/profile interaction or vpc_ids filtering behavior).

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?

States the basic action (describe) and resource (VPCs) with scope (in the account), but is minimal and borderline tautological with the function name. Does not explain what 'describe' entails (list attributes, metadata, etc.).

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?

Provides no guidance on when to use this tool versus sibling tools like aws_vpc_describe_subnets or aws_ec2_describe_instances. No mention of when to filter with vpc_ids parameter versus retrieving all VPCs.

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