AWS MCP Server

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

Annotations indicate this is a write operation (readOnlyHint: false) and non-destructive (destructiveHint: false), but the description adds minimal context beyond 'Create'. It doesn't explain what happens after creation (e.g., default routes, association requirements) or mention the openWorldHint: true annotation's implications. No contradiction with annotations exists.

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 that directly states the tool's purpose without unnecessary words. It's appropriately front-loaded with the core action and resource.

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 creation tool with complex nested parameters (RouteTableArgs), no output schema, and annotations that don't fully explain behavior (e.g., openWorldHint implications), the description is inadequate. It lacks details on what the tool returns, error conditions, or how it integrates with other AWS components, making it incomplete for 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 50%, with the 'region' parameter well-documented but 'RouteTableArgs' having nested properties. The description adds no parameter semantics beyond implying a region is needed. It doesn't clarify the purpose of VpcId, TagSpecifications, DryRun, or ClientToken, leaving significant gaps in understanding the input requirements.

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 ('Create') and resource ('route table'), and specifies the region context ('in the given region'). However, it doesn't differentiate from sibling tools like 'create-vpc' or 'create-subnet' beyond the resource type, which are all AWS infrastructure creation tools with similar patterns.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing VPC), related operations (e.g., associating routes), or sibling tools like 'associate-route-table' or 'delete-route-table' that might be used in conjunction.

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