AWS MCP Server

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

No annotations provided, so description carries full burden. States 'List' implying read-only, but fails to disclose pagination behavior, default limits, return value structure, or whether results are complete vs. truncated when max_results is hit.

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 4 words. No wasted words or redundancy. However, given zero annotations and missing output schema, the extreme brevity leaves significant gaps, preventing a 5.

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?

Incomplete for a 4-parameter tool with no output schema. Missing description of return values (database names, ARNs, or full objects?), pagination token handling, and the relationship between catalog_id and the account default.

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 4 parameters (profile, region, catalog_id, max_results). The description adds no parameter-specific guidance, but baseline 3 is appropriate 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?

Clear verb 'List' and specific resource 'Glue Data Catalog databases'. However, it does not explicitly differentiate from sibling tool aws_athena_list_databases or other Glue tools like aws_glue_get_tables in the description text itself, though the name helps.

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 on when to use this tool versus alternatives (e.g., aws_athena_list_databases), no mention of prerequisites (AWS credentials via profile), and no exclusions or contextual triggers.

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