AWS MCP Server

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

Annotations already provide key hints: destructiveHint=true, readOnlyHint=false, idempotentHint=true, and openWorldHint=true. The description adds minimal context beyond this, but it doesn't contradict annotations. It could enhance transparency by noting irreversible deletion or bucket emptiness requirements, but it's not misleading.

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 an S3 bucket') with essential context ('in the given region'). There is zero waste, making it appropriately sized and well-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?

Given the tool's complexity (destructive operation with 2 parameters, no output schema, and rich annotations), the description is minimal. It covers the basic action but lacks details on outcomes, error conditions, or dependencies (e.g., bucket must be empty). Annotations help, but more context would improve completeness.

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% (only 'region' has a description, 'Bucket' does not). The description mentions 'region' and implies 'Bucket' through context, but doesn't add detailed semantics like bucket naming rules or region defaults beyond the schema. It partially compensates for low coverage but not fully.

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 ('an S3 bucket') with regional context ('in the given region'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'delete-vpc' or 'delete-subnet', which also delete AWS resources, so it misses full sibling distinction.

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, such as 'list-buckets' for checking existence or 'create-bucket' for creation. It lacks explicit when/when-not statements or prerequisites, leaving usage context implied at best.

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