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 the exact state change ('sets is_paused=False'), describes the return format, and mentions error handling. While annotations already indicate destructiveHint=true, the description provides concrete implementation details about what gets changed and what's returned.

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 efficiently structured with a clear purpose statement followed by organized parameter and return sections. Every sentence adds essential information with zero waste. The two-sentence purpose statement covers both action and return value effectively.

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 destructiveHint annotation and the presence of an output schema, the description provides excellent context: it explains the state mutation, parameter relationships, return format, and error handling. For a destructive operation with good annotations and output schema, this description is complete and helpful.

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 fully compensates by explaining all three parameters: their purposes (instance key, UI URL resolution, DAG identifier), optionality, mutual exclusivity rules, and precedence. It provides complete semantic understanding 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 specific action ('Resume DAG scheduling'), the effect ('sets is_paused=False'), and distinguishes it from siblings like 'airflow_pause_dag' by being the opposite operation. It provides both the functional behavior and the return value structure.

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 parameter usage guidance (instance vs ui_url mutual exclusivity, dag_id requirement when ui_url not provided) and implies usage context through the action name 'unpause'. However, it doesn't explicitly state when to use this tool versus alternatives like 'airflow_pause_dag' or 'airflow_trigger_dag'.

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