AWS MCP Server

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

No annotations are provided, placing full burden on the description. While 'Get' implies read-only access, the description does not explicitly confirm this is safe (non-destructive), does not describe what details are returned (capacity, status, instance types, autoscaling config), nor mention AWS credential requirements or region handling behavior.

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 concise at six words in a single sentence. No waste, but also minimal value delivered. Structure is flat without front-loading of key distinctions (e.g., 'Get details for a specific EKS managed node group [vs list operation]...').

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?

With 100% input schema coverage and no output schema, the description meets minimum requirements but leaves significant gaps. For an AWS describe operation, should indicate what information is returned (configuration, health, scaling status) and clarify relationship to listing operations. Adequate but clearly incomplete.

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 all four parameters (profile, region, cluster_name, nodegroup_name) fully documented in the schema itself. The description adds no parameter-specific context, but per rubric, baseline is 3 when schema descriptions are comprehensive. No mention that cluster_name and nodegroup_name are required identifiers or that profile/region are optional overrides.

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' and resource 'EKS managed node group details', clearly indicating a read operation on a specific resource. However, it lacks explicit differentiation from sibling tool aws_eks_list_nodegroups, which operates on the same resource type but returns a collection rather than details.

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 guidance provided on when to use this versus aws_eks_list_nodegroups (for enumeration) or aws_eks_describe_cluster (for parent cluster details). No mention of prerequisites like needing the cluster_name first or typical use cases such as troubleshooting node group configuration.

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