AWS MCP Server

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

No annotations provided, so description carries full behavioral disclosure burden. 'List' implies read-only but doesn't confirm lack of side effects, required IAM permissions, pagination behavior, or error handling (e.g., non-existent parameter group).

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 6 words with zero waste. Front-loaded with action verb and resource. Every word earns its place.

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?

Minimum viable for this complexity level. With fully documented schema and simple string parameters, the description suffices for basic invocation. However, lacks operational context expected for AWS services (permissions, throttling, pagination) and has no output schema to reference.

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 description coverage is 100%, so baseline applies. The description adds minimal semantic meaning beyond what the schema already provides for the four parameters (profile, region, parameter_group_name, source).

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 the specific action ('List') and target resource ('parameters for a Redshift parameter group'). Implicitly distinguishes from sibling 'aws_redshift_describe_clusters' by referencing 'parameter group' instead of 'clusters', though explicit contrast would strengthen this.

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 provided on when to use versus alternatives, prerequisites (e.g., needing to obtain parameter_group_name from elsewhere), or typical workflow context.

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