AWS MCP Server

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

No annotations provided and description offers minimal behavioral disclosure. Does not indicate if this is read-only (implied but not explicit), whether results are paginated, what fields are returned, or any rate limiting constraints.

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 brief single sentence with no waste, but arguably under-specified given lack of annotations and output schema. Front-loading is adequate with the essential verb-resource pair.

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 no description of return values or pagination behavior, the definition leaves significant gaps. Relies entirely on well-documented input schema but fails to explain what constitutes an 'environment' or how to interpret results.

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 parameter descriptions, establishing baseline of 3. Description adds '(Apache Airflow)' context which helps explain the resource type, but does not elaborate on parameter interactions (e.g., how max_results affects pagination).

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 clear verb (List) and resource (MWAA environments) with helpful acronym expansion to Apache Airflow. However, fails to distinguish from sibling tool aws_mwaa_get_environment (list all vs. get specific).

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 the sibling get_environment tool, or when pagination (max_results) is needed. No prerequisites or alternatives mentioned.

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