AWS MCP Server

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

With no annotations provided, the description carries the full burden of disclosure. It reveals what data categories are returned (delivery attempts, bounces, complaints, rejects) but omits critical behavioral details: the time aggregation period (15-minute intervals), the lookback window (14 days), whether data is near-real-time or delayed, and required IAM permissions.

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 single sentence is efficiently front-loaded with the action verb and resource, immediately followed by the specific metric categories returned. No extraneous words are present and every clause earns its place.

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 lack of output schema and annotations, the description partially compensates by enumerating the return data categories. However, for a statistics retrieval tool, it fails to mention the temporal aggregation granularity or time range limitations, leaving significant gaps in contextual understanding.

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?

The description makes no mention of the parameters, but with 100% schema description coverage for both optional parameters ('profile' and 'region'), the baseline score of 3 applies as the schema adequately documents inputs without requiring description reinforcement.

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 uses a specific verb ('Get') and resource ('SES sending statistics'), and distinguishes the tool by listing specific metric types (delivery attempts, bounces, complaints, rejects). However, it does not explicitly differentiate from the sibling tool 'aws_ses_get_send_quota' which retrieves limits rather than historical statistics.

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, nor does it mention prerequisites such as requiring prior email sending activity for statistics to exist. No temporal scope (e.g., 'last 14 days') is indicated to help users understand data availability.

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