AWS MCP Server

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

No annotations provided, so description carries full disclosure burden. While it states what is retrieved (verification status), it fails to describe specific returned attributes (e.g., VerificationStatus, VerificationToken), error handling for non-existent identities, or AWS API rate limit considerations.

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 efficient sentence that is front-loaded with the verb and resource. Zero redundancy or wasted words.

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?

No output schema exists, yet the description fails to describe the return structure or specific verification attributes returned. For a 3-parameter AWS API tool with no annotations, the description is incomplete regarding behavioral outcomes and return value semantics.

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 has 100% description coverage. The description reinforces that identities are 'email addresses and domains' but adds no syntax details, format constraints, or usage examples beyond what the schema already provides.

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?

Clear verb 'Get' and specific resource 'verification status for SES identities', with clarification that identities include 'email addresses and domains'. Implicitly distinguishes from sibling 'list_identities' by focusing on verification attributes rather than mere enumeration.

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?

Provides no guidance on when to use this versus 'list_identities' or other SES tools, no prerequisites stated (e.g., that identities must already be registered in SES), and no mention of error scenarios or alternatives.

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