AWS MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate whether this operation is read-only (though implied by 'describe'), what the return structure looks like (list of snapshots vs. single object), pagination behavior with max_results, or any rate limiting concerns. No mention of whether results are cached or real-time.

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 terse 3-word sentence with zero redundancy. However, it suffers from under-specification rather than efficient conciseness—it lacks the informational density expected for a tool with 5 optional parameters and no output schema. Every word earns its place, but there are too few 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?

Given the lack of annotations and output schema, the description should compensate with richer context about return values, authentication requirements, and service-specific behaviors. It provides none of these, leaving significant gaps for an AI agent attempting to understand the tool's full contract.

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 100% schema description coverage, the parameters are fully documented in the structured schema (profile, region, filters). The description adds no additional semantic information about parameter interactions or syntax, but the high schema coverage warrants the baseline score of 3.

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 'Describe MemoryDB snapshots' is essentially a tautology that restates the tool name with spaces added. While it identifies the target resource (MemoryDB snapshots), it fails to distinguish from similar sibling tools like aws_redshift_describe_cluster_snapshots or aws_rds_describe_db_snapshots, and provides no scope clarification (list vs. get single item).

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 note that all parameters are optional (allowing broad listing versus specific filtering). There is no mention of required IAM permissions, prerequisites, or relationships to other MemoryDB operations like cluster management.

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