AWS MCP Server

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

No annotations are provided, and the description adds no behavioral context beyond the action itself. It omits disclosure about read-only safety (implied by 'List' but not confirmed), pagination behavior, required IAM permissions, or error scenarios when the cluster doesn't exist.

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 efficiently structured with the action front-loaded. While there is no wasted text, the extreme brevity leaves significant gaps in contextual information that could have been added without sacrificing clarity.

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?

For an AWS EKS operation with no output schema and no annotations, the description is minimally adequate. It identifies the target resource but fails to explain what constitutes a Fargate profile, expected return format, or AWS-specific behaviors, relying entirely on the parameter schema for substance.

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 parameters (profile, region, cluster_name) are fully documented in the schema. The description adds no additional semantic value regarding parameter interactions or validation rules, meeting the baseline for high-coverage schemas.

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 provides a clear verb ('List') and specific resource ('Fargate profiles for an EKS cluster'), distinguishing it from siblings like 'aws_eks_list_clusters' and 'aws_eks_list_nodegroups' by specifying the Fargate-specific resource type. However, it lacks scope details like pagination behavior or filtering capabilities.

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 offers no guidance on when to use this tool versus alternatives, prerequisites such as requiring an existing cluster, or error conditions (e.g., cluster not found). It states what it does but not when or why to choose it.

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