AWS MCP Server

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

With no annotations provided, the description carries full disclosure burden but fails to state this is a read-only operation, does not describe what data is returned when serverless_cache_name is omitted (list all), and omits any mention of rate limits or AWS API throttling 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, efficiently structured sentence with resource type front-loaded and clarifying scope (Redis/Memcached) in parentheses. No redundant or wasted text despite minimalism.

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?

Lacks critical behavioral context expected for a 4-parameter AWS query operation with no output schema or annotations. Should disclose return value structure, pagination behavior, and safety characteristics (read-only) given absence of structured metadata.

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 (all 4 parameters documented), establishing baseline of 3. The tool description adds no parameter-specific context (e.g., no syntax guidance for profile strings or pagination logic for max_results) 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?

Provides specific verb (Describe) and resource (ElastiCache Serverless caches), and parenthetically clarifies supported engine types (Redis/Memcached). Effectively distinguishes from sibling tools like 'describe_cache_clusters' by explicitly scoping to 'Serverless' resources.

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?

Contains no guidance on when to use this tool versus its siblings (e.g., when to use specific name filtering vs. listing all), nor does it explain pagination behavior with max_results or regional filtering strategies.

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