AWS MCP Server

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

The description doesn't contradict annotations, which already indicate destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=true. It adds minimal behavioral context beyond annotations by specifying the region parameter. However, for a destructive operation, it could better explain implications like irreversible deletion or dependency checks.

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 front-loads the core action ('Delete a route table') and includes essential context ('in the given region'). There is no wasted verbiage or redundancy, making it easy to parse quickly.

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 the tool's destructive nature (destructiveHint=true), no output schema, and 50% schema coverage, the description is minimally adequate. It covers the basic purpose but lacks details on usage context, error handling, or output expectations. For a high-stakes deletion tool, more completeness would be beneficial.

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' nested object lacking detailed descriptions. The description mentions 'region' but doesn't clarify parameter roles or interactions (e.g., that 'DryRun' validates permissions without execution). It adds some meaning by emphasizing region, but doesn't fully compensate for the schema gaps.

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 ('Delete') and resource ('a route table'), and specifies the region context ('in the given region'). It distinguishes from siblings like 'disassociate-route-table' by focusing on deletion rather than disassociation. However, it doesn't explicitly differentiate from other delete operations like 'delete-vpc' or 'delete-subnet' beyond the resource type.

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. It doesn't mention prerequisites (e.g., route table must be disassociated first), consequences (e.g., impact on network routing), or when to choose deletion over modification. With siblings like 'disassociate-route-table' and 'replace-route-table-association', this gap is significant.

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