Get a diagnostic checklist for a DAG to identify issues in runs, tasks, or logs. Specify a context or resource to receive a structured analysis, helping you pinpoint failures and improve workflow reliability.
Diagnostics / checklist for dags.
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Context or resource |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Diagnostics / checklist for dags,' which neither confirms whether this is a read-only operation, nor describes what outputs, errors, or side effects to expect. The behavioral surface is essentially undisclosed.
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 extremely short, but this reads as under-specification rather than effective conciseness. It is a fragment with no sentence structure and omits essential details such as what the diagnostics cover, how context is used, and what the output looks like.
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?
The tool is simple, with one optional parameter and no output schema, but the description still leaves major gaps: it does not explain what the diagnostic checklist evaluates, what a successful result would contain, or how this relates to the sibling status/list/get tools. This is insufficient for reliable invocation.
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 100% because the parameter 'context' has the description 'Context or resource.' The tool description adds no parameter-level meaning, but the schema already documents the only parameter, so this is an acceptable baseline despite the descriptor being vague.
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 'Diagnostics / checklist for dags' names the resource (DAGs) and a general intention, which distinguishes it somewhat from the siblings airflow_status, airflow_list, and airflow_get. However, it is a noun phrase rather than a verb-led statement and does not specify what kind of diagnostics or checklist is provided, leaving the actual function ambiguous.
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?
There is no guidance on when to use this tool versus airflow_status, airflow_list, or airflow_get. No conditions, exclusions, or alternative-selection hints are given, so the agent must infer the tool's role from its name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.