AWS MCP Server

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

The description adds no behavioral information beyond what annotations already provide. Annotations clearly indicate destructiveHint=true (mutation), readOnlyHint=false (write operation), and idempotentHint=true (safe to retry). The description doesn't mention AWS-specific behaviors, error conditions, or what happens when tags don't exist. However, it doesn't contradict the annotations either.

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?

While technically concise with just three words, this is under-specification rather than effective brevity. The description fails to provide necessary context for a destructive operation. Every word earns its place, but there aren't enough words to be helpful - it's incomplete rather than efficiently structured.

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 destructive tool with complex nested parameters (InstanceArgs object containing Resources array, Tags array with Key/Value objects, and DryRun boolean), no output schema, and only 50% schema coverage, this description is severely inadequate. It doesn't explain what gets deleted, from what resources, under what conditions, or what the expected outcome is.

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?

With only 50% schema description coverage, the description provides zero parameter information to compensate. The schema documents 'region' and 'InstanceArgs' with sub-properties, but the description doesn't explain what these parameters mean, how they interact, or provide any context about AWS-specific requirements. This leaves significant gaps in parameter understanding.

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 instance tag' is a tautology that merely restates the tool name without adding meaningful context. It doesn't specify what type of instance (EC2 instance), what resource the tag is being deleted from, or how this differs from sibling tools like 'delete-ami' or 'delete-db-instance'. While the verb 'delete' is clear, the resource scope is ambiguous.

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 absolutely no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when this operation is appropriate, or how it differs from other deletion tools like 'delete-ami' or 'delete-db-instance'. The agent receives no contextual framing for this destructive operation.

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