AWS MCP Server

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

No annotations provided, so description carries full burden. 'Get' implies read-only operation but lacks explicit safety confirmation, error behavior (e.g., what happens if ARN is invalid), or pagination details. Does not mention what health states are returned (healthy, unhealthy, etc.).

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 sentence of 10 words with action front-loaded. No redundancy or tangential information. Every word earns its place by conveying the core operation, scope, and target resource.

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 read operation with 100% parameter schema coverage. Clearly identifies the AWS service (ELBv2) operation via naming and describes the retrieval scope. Missing only output format details and specific health state values, but acceptable for a describe tool without output schema.

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 has 100% description coverage (profile, region, target_group_arn all documented). Description mentions 'target group' which loosely maps to target_group_arn parameter, but adds no syntax details or examples beyond what the schema already provides. Baseline 3 appropriate for high schema coverage.

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 specific verb 'Get' with clear resources 'health status' and 'targets registered in a target group'. It effectively distinguishes from sibling aws_elbv2_describe_target_groups (which describes group configuration) by specifying 'health status' of the targets within the group.

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 provided on when to use this tool versus alternatives like describe_target_groups. No mention of prerequisites such as needing to obtain the target_group_arn from another operation first, or common usage patterns.

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