AWS MCP Server

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

No annotations are provided, so the description carries full disclosure burden. While 'List' implies read-only behavior, the description fails to mention critical AWS API behaviors such as pagination (MaxResults/NextToken), API rate limiting, or the structure/format of returned target group data.

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 single-sentence description is front-loaded with the core action but is excessively terse for a 5-parameter AWS operation with no output schema. While there is no wasted text, the extreme brevity omits necessary behavioral context that would make it genuinely useful.

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?

Given the tool has 5 parameters, no annotations, and no output schema, the description is insufficient. It fails to document what data is returned (target group ARNs, names, health check settings, etc.), pagination behavior, or AWS-specific constraints, leaving significant gaps for an AI agent to operate effectively.

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?

With 100% schema description coverage, the baseline is 3. The description mentions 'filtered by load balancer' which maps to the load_balancer_arn parameter, but it fails to add semantic context for the other three filter parameters (target_group_arns, names) or explain parameter interactions (e.g., that all filters are optional and combinable).

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 clearly states the verb (List) and resource (target groups) and mentions the optional filter by load balancer. However, it does not explicitly distinguish this tool from the sibling 'aws_elbv2_describe_target_health', which retrieves health status of targets rather than listing the target groups themselves.

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 minimal guidance with 'optionally filtered by load balancer', hinting at a use case (finding target groups for a specific LB). However, it lacks explicit when-to-use guidance, prerequisites, or clear differentiation from related ELBv2 siblings like describe_target_health or describe_listeners.

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