AWS MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to state that this is a read-only operation, does not describe pagination behavior despite the presence of a 'limit' parameter, and omits any mention of return value structure or AWS permission requirements.

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?

The description is a single, efficient sentence with zero waste. Every word earns its place by identifying the operation and resource type.

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?

While the description adequately identifies the target resource for a simple list operation, it lacks completeness given the absence of annotations and output schema. It omits return value details, pagination behavior, and the required scope filtering context that would help an agent invoke the tool correctly.

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%, establishing a baseline of 3. The description adds slight semantic value by mentioning 'managed and custom' rule groups (clarifying the resource types), but does not elaborate on parameter interactions (e.g., that 'scope' is required and filters the results by deployment type).

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?

The description uses a specific verb ('List') and identifies the exact resource ('WAF v2 managed and custom rule groups'), distinguishing it from sibling tools like aws_wafv2_list_web_acls and aws_wafv2_list_ip_sets. However, it does not explicitly clarify the scope of the operation (e.g., per-region) or prerequisites.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., aws_wafv2_get_web_acl for individual ACL details), nor does it mention the required 'scope' parameter or when pagination via 'limit' is necessary.

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