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 disclosure burden but provides minimal behavioral context. It does not indicate read-only safety, pagination behavior (despite max_results parameter), default result limits, or what constitutes a valid cluster name format.

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?

Extremely concise at four words with no redundancy. However, the brevity borders on under-specification given the tool's complexity (4 parameters, AWS service interaction), leaving little structural context for the agent.

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?

Inadequate for a 4-parameter AWS service tool lacking both annotations and output schema. The description omits return value structure, authentication requirements, and error conditions that the agent needs to invoke the tool effectively.

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?

Input schema has 100% description coverage with clear definitions for profile, region, cluster_name, and max_results. The description adds no parameter-specific guidance, but the high schema coverage meets the baseline expectation.

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 states the verb (Describe) and resource (MemoryDB for Redis clusters), identifying the specific AWS service. However, it lacks scope clarification—whether it retrieves one cluster or many, or what specific attributes are returned—leaving ambiguity given the optional cluster_name parameter.

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 is provided on when to use this versus the sibling tool aws_memorydb_describe_snapshots, or when to apply filtering via cluster_name versus retrieving all clusters. No prerequisites (AWS credentials, permissions) are mentioned.

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