Apache Airflow MCP Server

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

The description adds valuable behavioral context beyond annotations: it specifies that the tool returns a UI link and details the response structure and error handling. Annotations already indicate it's destructive and not idempotent, but the description enhances understanding with practical outcomes like the UI link return.

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?

The description is front-loaded with the core purpose, followed by organized sections for parameters and returns. Every sentence adds value—no redundancy or fluff—making it efficient and easy to parse.

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?

Given the tool's complexity (destructive mutation, 3 parameters) and the presence of an output schema (which covers return values), the description is complete. It explains the action, parameter logic, and response format adequately, leaving no significant gaps for agent understanding.

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?

With 0% schema description coverage, the description compensates well by explaining parameter roles and constraints: 'instance' and 'ui_url' are optional and mutually exclusive, 'dag_id' is conditionally required, and 'ui_url' takes precedence. This adds meaningful semantics beyond the bare schema.

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?

The description clearly states the tool's purpose with a specific verb ('Pause DAG scheduling') and resource ('DAG'), and distinguishes it from sibling tools like 'airflow_unpause_dag' by specifying the opposite action. The mention of setting 'is_paused=True' adds technical precision.

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?

The description provides clear context on when to use this tool (to pause DAG scheduling) and includes parameter-specific guidance (e.g., 'dag_id' is required if 'ui_url' not provided, 'ui_url' takes precedence). However, it lacks explicit when-not-to-use guidance or alternatives compared to siblings like 'airflow_unpause_dag'.

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