AWS MCP Server

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

Annotations cover key behavioral traits (destructive, idempotent, open-world), so the bar is lower. The description adds minimal context beyond annotations—it specifies the region parameter but doesn't explain deletion effects (e.g., irreversible, impact on instances) or permissions. 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, direct sentence with zero wasted words, front-loading the core action and resource. It's appropriately sized for a simple deletion tool, 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 destructive nature (annotations cover this), lack of output schema, and 50% schema coverage, the description is minimal but functional. It states the action and region, but for a destructive tool, more context on consequences or error handling would improve completeness. Annotations help, but the description could add more value.

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 'KeyPairArgs' documented in the schema. The description mentions 'region' but adds no details beyond the schema's default and description. It doesn't clarify parameter interactions (e.g., using KeyPairId vs. KeyName) or compensate for the coverage gap.

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 key pair') with regional context ('in the given region'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'delete-ami' or 'delete-bucket' beyond the resource type, which is implied but not explicit.

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 like 'import-key-pair' or 'create-key-pair', nor does it mention prerequisites (e.g., needing the key pair ID or name). The description only states what it does, not when or why to use it.

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