AWS MCP Server

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

No annotations provided. Description adds crucial behavioral constraint that query must be 'completed', indicating a state prerequisite. Missing disclosure of pagination behavior (despite max_results parameter), result format/columnar structure, and download size limits inherent to Athena result retrieval.

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 7-word sentence is extremely front-loaded with zero redundancy. However, brevity is excessive given lack of annotations and pagination complexity; one additional sentence for behavioral constraints would improve utility without harming conciseness.

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 output schema and no annotations, description successfully identifies the core operation but leaves significant gaps for a paginated data retrieval tool. Should specify result format (CSV, JSON), pagination token handling, and integration with the sibling status-checking tool to be complete.

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 has 100% description coverage, fully documenting all four parameters including profile/region overrides and max_results. Description adds no parameter-specific guidance beyond what schema provides, earning baseline score for high-coverage schemas.

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 'Get' and resource 'results of a completed Athena query execution' specifies exactly what is retrieved. Distinguishes from sibling 'aws_athena_get_query_execution' by specifying 'results' (data rows) versus execution metadata, though explicit comparison is not stated.

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?

Specifies prerequisite state 'completed' implying this should not be called on running queries. However, lacks explicit workflow guidance (e.g., 'use aws_athena_get_query_execution first to verify completion') and does not mention error behavior if called prematurely.

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