AWS MCP Server

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

No annotations provided, so description carries full burden. While 'Get' implies read-only safety, description omits key behavioral details: error handling for non-existent clusters, AWS API rate limit considerations, or whether this operation incurs costs.

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 single sentence with no redundancy. However, given zero annotations and no output schema, the description is arguably too minimal and front-loaded with insufficient information density.

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?

Inadequate for a 3-parameter AWS API tool with no output schema and no annotations. Should specify what detailed information is returned (status, capacity, registered instances) or clarify the typical workflow with list_clusters.

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 description coverage is 100%, establishing baseline 3. Description mentions 'one or more' which maps to the array requirement of the 'clusters' parameter, but adds no further semantic details (e.g., expected format of ARNs) beyond schema documentation.

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?

Uses specific verb 'Get' and resource 'ECS clusters', with 'detailed information' distinguishing it from sibling aws_ecs_list_clusters. However, lacks explicit differentiation regarding prerequisites (i.e., that cluster names/ARNs must be obtained first via list_clusters).

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 no guidance on when to use this tool versus alternatives. Critical prerequisite relationship with aws_ecs_list_clusters (which supplies the cluster identifiers required by this tool) is not mentioned.

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