AWS MCP Server

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

Annotations provide key behavioral hints: destructiveHint=true (indicating permanent deletion), idempotentHint=true (safe to retry), and readOnlyHint=false (confirms it's a mutation). The description adds no behavioral context beyond 'Delete an AMI', such as irreversible consequences, permissions needed, or AWS-specific constraints. With annotations covering safety and idempotency, a baseline 3 is appropriate, but the description misses opportunities to add value like warning about associated snapshots or dry-run usage.

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 extremely concise with a single sentence, 'Delete an AMI', which is front-loaded and wastes no words. For a tool with clear annotations and schema, this brevity is efficient, though it may sacrifice helpful context.

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 complexity (destructive operation with nested parameters) and lack of output schema, the description is insufficient. It doesn't explain return values, error conditions, or critical context like the impact of 'DeleteAssociatedSnapshots'. Annotations help, but for a high-stakes deletion tool, more guidance is needed to ensure safe and correct usage.

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 parameters like 'region' and 'AmiArgs.ImageId' described, but 'DeleteAssociatedSnapshots' and 'DryRun' lack schema descriptions. The description provides no parameter information, failing to compensate for the coverage gap. Since the schema handles half the parameters adequately, the baseline is 3, but the description adds zero value beyond what's in the 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 description 'Delete an AMI' clearly states the verb (delete) and resource (AMI), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'terminate-ec2-instance' or other delete operations, nor does it specify what AMI stands for (Amazon Machine Image). It's adequate but lacks specificity about scope or differentiation.

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. There's no mention of prerequisites (e.g., AMI must not be in use), when to avoid it, or how it relates to siblings like 'list-amis' or 'create-ami'. This leaves the agent without context for appropriate tool selection.

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