AWS MCP Server

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

No annotations provided, so description carries full burden. Only behavioral hint is 'manual and automated' scope. Lacks critical AWS context: pagination behavior with max_records, default behavior when cluster_identifier omitted (all clusters?), IAM permissions needed, or return structure.

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 sentence, zero redundancy, front-loaded with verb and resource. Efficient structure, though arguably under-specified rather than optimally concise given AWS complexity.

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 5-parameter AWS tool with no output schema. Missing: pagination token behavior, default scope when filters omitted, IAM permissions (redshift:DescribeClusterSnapshots), and whether results include encrypted snapshot indicators. High schema coverage saves parameter documentation, but operational context is absent.

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 with clear AWS-centric descriptions. With high schema coverage, baseline is 3. Description adds no parameter-specific context (no examples, no format clarification, no cross-parameter dependencies), but schema adequately documents inputs.

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?

States specific verb 'List' and resource 'Redshift cluster snapshots'. Parenthetical '(manual and automated)' adds scope clarity. Distinguishes from sibling aws_redshift_describe_clusters by specifying 'snapshots' vs 'clusters', though terse.

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 vs alternatives, when filtering by cluster_identifier is required vs optional, or prereqs like IAM permissions. Zero alternatives or exclusions mentioned.

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