AWS MCP Server

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

No annotations provided, so description carries full burden. While 'List' implies read-only behavior, it fails to disclose that this returns parameter metadata (names, types, tiers) but not actual values, or describe pagination behavior given the lack of output schema.

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 with action-fronted structure. No redundant words or repetition of the tool name. Appropriate length for the complexity level.

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?

Adequate for a listing tool with well-documented parameters, but gaps remain: no output schema exists and the description doesn't compensate by describing return values, pagination tokens, or throttling considerations. Sibling tool relationships unexplored.

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 coverage is 100% with clear descriptions for all 4 parameters including an example JSON for filters. Description text mentions 'optional filters' but adds no semantic detail beyond what the schema already provides, warranting the baseline score.

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 ('List') and resource ('SSM Parameter Store parameters'), but lacks explicit differentiation from siblings like aws_ssm_get_parameter (single item retrieval) or aws_ssm_get_parameters_by_path (hierarchical retrieval). The mention of 'optional filters' provides implicit context for bulk operations.

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 explicit guidance on when to use this tool versus alternatives (get_parameter for specific values, get_parameters_by_path for hierarchy). Only minimal guidance implied by 'optional filters'.

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