AWS MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to clarify read-only safety, pagination behavior (despite the max_results parameter), return format, or error conditions. The agent cannot determine if this is a simple list call or requires specific setup.

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?

While efficient at three words without verbosity, it is under-specified rather than appropriately concise. Given the tool's complexity (AWS service integration, 3 optional parameters, no output schema), the extreme brevity fails to provide necessary context, making it insufficiently informative.

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 no annotations, no output schema, and a minimal description, critical contextual gaps remain. The agent cannot determine what workgroup attributes are returned, how pagination works, or what permissions are required. For an AWS integration tool, this is inadequate.

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%, providing detailed descriptions for profile, region, and max_results. The description adds no semantic value beyond the schema (it doesn't explain that max_results limits pagination or how profile names map to AWS config files), warranting the baseline score of 3.

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?

States a clear verb ('List') and resource ('Athena workgroups'), so the purpose is immediately comprehensible. However, it lacks scope details (e.g., whether it returns all workgroups or supports pagination) and does not differentiate from other Athena listing tools like aws_athena_list_databases.

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, nor does it mention prerequisites like AWS credentials or IAM permissions required to view workgroups. The description offers zero usage context beyond the action itself.

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