Apache Airflow MCP Server

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

Annotations indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds value by specifying the return structure and error handling ('Raises: ToolError with compact JSON payload'), which provides context beyond annotations. However, it lacks details on rate limits, authentication needs, or performance traits.

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 and concise, with a clear purpose statement followed by parameter and return details in bullet-like format. Every sentence adds value (e.g., explaining returns and errors), though it could be slightly more front-loaded by emphasizing the core use case earlier.

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 (parsing URLs with multiple identifiers), annotations cover safety, and an output schema exists (implied by 'Returns' details), the description is reasonably complete. It explains the response dict and error handling, addressing key behavioral aspects. However, it could benefit from more context on integration with sibling tools or example use cases.

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?

The input schema has 0% description coverage, with one parameter 'url' of type string. The description adds minimal semantics by noting it's an 'Airflow UI URL (http/https)', which clarifies the expected format. This compensates slightly for the low schema coverage, but doesn't detail URL patterns or validation rules, keeping it at a baseline level.

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: 'Parse an Airflow UI URL, resolve instance and identifiers.' This specifies the verb (parse/resolve) and resource (Airflow UI URL), making it understandable. However, it doesn't explicitly differentiate from sibling tools (e.g., airflow_describe_instance or others that might handle URLs), which prevents a perfect score.

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 mentions parameters and returns but doesn't specify use cases, prerequisites, or exclusions. For example, it doesn't clarify if this is for validation, preprocessing, or integration with other Airflow tools, leaving usage ambiguous.

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