AWS MCP Server

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

Annotations indicate this is a mutable operation (readOnlyHint: false) with open-world semantics (openWorldHint: true) and non-destructive (destructiveHint: false). The description adds no behavioral context beyond the annotations—it doesn't mention permissions, rate limits, idempotency (idempotentHint: false), or what 'import' specifically does (e.g., adding an existing key pair to AWS). With annotations covering safety but not operational details, the description fails to add meaningful value.

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 function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly. No sentence is wasted, achieving optimal conciseness for such a simple statement.

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 (mutation with nested objects, no output schema) and moderate annotation coverage, the description is inadequate. It lacks details on what 'import' means operationally, expected outcomes, error conditions, or how it differs from sibling tools. Without output schema or rich behavioral disclosure, the description leaves significant gaps for an agent to use the tool effectively.

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 implies a region parameter but adds no semantic details beyond the schema, such as explaining 'KeyPairArgs' structure or when to use 'DryRun'. Since the schema covers half the parameters adequately, the description meets the baseline but doesn't 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 states the action ('import') and resource ('key pair') with a location constraint ('in the given region'), which is clear but basic. It doesn't differentiate from sibling tools like 'create-key-pair' or 'list-key-pairs', leaving ambiguity about when to use import versus create. The purpose is understandable but lacks specificity about what 'import' entails compared to alternatives.

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 'create-key-pair' or 'list-key-pairs'. The description mentions a region parameter but doesn't explain prerequisites, such as needing an existing public key to import. Without usage context or exclusions, the agent must infer when this tool is appropriate.

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