AWS MCP Server

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

With zero annotations provided, the description carries full burden but omits critical AWS behavioral details: no mention of pagination (NextToken/continuation), throttling considerations, or what fields are returned (IP addresses, names, IDs). The '(allow/block lists)' parenthetical adds semantic context for IP set purpose but insufficient operational detail.

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 efficient 6-word description front-loaded with action verb and resource type. Parenthetical adds value without verbosity. No redundant phrases or structural waste.

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 simple list operation with complete input schema, but lacks output context (no output schema provided). Missing pagination behavior mention which is critical for AWS list operations that may require iteration via NextToken.

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 (profile, region, scope, limit). The description does not add parameter-specific semantics beyond the schema, so baseline 3 applies.

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 'WAF v2 IP sets' with parenthetical context '(allow/block lists)' that clarifies the resource's purpose. Differentiates from siblings like list_web_acls and list_rule_groups by specifying 'IP sets', though does not explicitly name alternatives or contrast with get_web_acl.

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 versus retrieving specific IP sets (e.g., get_ip_set) or how to choose between REGIONAL and CLOUDFRONT scope. Lacks prerequisites or conditional usage patterns despite being one of several WAFv2 listing tools.

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