AWS MCP Server

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

Annotations already indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=false, covering key behavioral traits. The description adds minimal context beyond annotations, mentioning region but not detailing irreversible consequences, permissions needed, or rate limits. 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?

Single sentence is appropriately concise for a straightforward deletion tool, front-loading the core action. No wasted words, though it could be slightly more informative without losing efficiency.

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 no output schema and incomplete parameter coverage, the description is inadequate. It lacks details on consequences (e.g., data loss, backups), error handling, or response format, leaving significant gaps for safe agent use.

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 'DBInstanceIdentifier' well-described in schema. The description adds no parameter semantics beyond implying region and DB instance are required, failing to compensate for coverage gaps (e.g., backup/snapshot behaviors). Baseline 3 applies as schema does moderate lifting.

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 ('RDS DB instance'), with regional context ('in the given region'). It distinguishes from siblings like 'terminate-ec2-instance' by specifying RDS DB instances, but doesn't explicitly differentiate from 'delete-db-instance' (no other DB deletion tool exists).

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 on when to use this tool versus alternatives like 'update-db-instance' or prerequisites. The description mentions region but doesn't specify when deletion is appropriate versus other operations. Siblings include 'list-db-instances' for discovery, but no explicit usage context is provided.

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