Apache Airflow MCP Server

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating a safe, repeatable read operation. The description adds value by specifying that it returns a UI link and a response dict structure, which aren't covered by annotations. However, it doesn't disclose additional behavioral traits like error handling, rate limits, or authentication needs beyond what annotations imply.

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 appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by structured sections for parameters and returns. Every sentence earns its place by providing essential information without redundancy. Minor improvements could include integrating usage context, but it's efficient overall.

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 moderate complexity (4 parameters, no required ones), rich annotations (safety hints), and an output schema (returns dict specified), the description is mostly complete. It covers purpose, parameters, and returns adequately. However, it lacks usage guidelines and deeper parameter semantics, which slightly reduces completeness for agent selection.

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 description coverage is 0%, so the schema provides no parameter details. The description lists parameters with brief explanations (e.g., 'Instance key (optional)'), adding basic semantics beyond the schema. However, it doesn't fully compensate for the coverage gap—it lacks details on parameter interactions, formats, or examples, leaving some ambiguity for the agent.

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: 'Get a single DAG run and a UI link.' It specifies the verb ('Get') and resource ('a single DAG run'), making it understandable. However, it doesn't explicitly differentiate from siblings like 'airflow_get_dag' or 'airflow_list_dag_runs' beyond the 'single' aspect, which is implied but not contrasted.

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 no guidance on when to use this tool versus alternatives. It lists parameters and returns but doesn't mention when to choose this over 'airflow_list_dag_runs' for multiple runs or 'airflow_get_dag' for DAG metadata. There's no context on prerequisites or exclusions, leaving usage unclear.

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