Apache Airflow MCP Server

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, repeatable read operation. The description adds valuable context beyond annotations by specifying the return format, error handling behavior ('Raises: ToolError with compact JSON payload'), and pagination details. It doesn't mention rate limits or authentication requirements, but provides good behavioral transparency given the annotations.

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 well-structured with clear sections (purpose, parameters, returns) and front-loaded with the core purpose. Every sentence adds value, though the parameter explanations could be slightly more concise. The structure helps the agent quickly understand the tool's functionality and usage.

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 (4 parameters, pagination, instance resolution), the description provides complete context. It explains the return format in detail, documents error handling, specifies parameter behaviors, and the existence of an output schema means the description doesn't need to exhaustively document return values. The combination of good description and annotations makes this 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?

With 0% schema description coverage, the description carries the full burden of explaining parameters. It provides comprehensive semantic information for all 4 parameters: explains the instance/ui_url mutual exclusivity and precedence rules, documents default values and coercion behavior for limit/offset, and clarifies that instance is optional. This fully compensates for the lack of schema descriptions.

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 verb ('List') and resource ('DAGs') with specific attributes ('pause state + UI link') and target scope ('for the target instance'). It distinguishes from siblings like airflow_list_dag_runs and airflow_list_task_instances by focusing specifically on DAGs rather than runs or task instances.

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 about when to use this tool ('List DAGs... for the target instance') and includes parameter guidance about mutual exclusivity and precedence. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools for different use cases.

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