AWS MCP Server

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

No annotations provided, yet description discloses no behavioral traits beyond the operation type. Missing: what metadata fields are returned (name, columns, partitions?), read-only safety confirmation, error behavior for invalid database_name, or pagination token handling.

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 with no redundancy. However, for a 5-parameter AWS integration tool with no output schema, this brevity leaves critical gaps rather than being optimally concise.

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 complexity level. No output schema exists, yet description doesn't hint at return structure. Lacks ecosystem context (Athena vs Glue catalog) and prerequisite relationships (requires valid database_name likely obtained via aws_athena_list_databases).

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 clear descriptions for all 5 parameters including profile, region, and catalog_name. The tool description itself adds no parameter semantics beyond the schema, but none are needed given complete 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?

States specific verb (List) and resource (tables in Athena database) clearly. However, it undersells compared to the tool name which includes 'metadata', and fails to distinguish from sibling aws_glue_get_tables which accesses the same underlying Glue Data Catalog.

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 versus aws_glue_get_tables or aws_athena_list_databases (likely prerequisite). No mention of pagination behavior despite max_results parameter implying result sets may be large.

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