airflow-get-task-instances

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

No annotations are provided, so the description carries the full burden. While 'list' suggests a read operation, the description does not explicitly state that it is read-only, nor does it disclose any behavioral traits such as pagination, filtering capabilities, or error handling. The description is minimal.

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 a single sentence that is front-loaded with the action and critical details. Every word serves a purpose; there is no redundancy or unnecessary information.

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 has two required parameters and no output schema, the description provides the basic purpose and lists some returned fields, but does not mention the return format, pagination behavior, error scenarios, or ordering. It is adequate for a simple list tool but lacks completeness.

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 coverage is 50% (only dagRunId has a description). The description mentions 'for a specific Airflow DAG run', which reinforces the parameter context but does not explain dagId. The description adds some value by clarifying the run's purpose, but does not fully compensate for the missing dagId description.

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 uses a specific verb ('List') and resource ('task instances') and explicitly ties it to a specific DAG run. It also mentions the fields returned (state, try_number, duration), making the tool's functionality very clear and differentiating it from siblings like airflow-get-task-logs or airflow-list-runs.

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 implies usage for listing task instances of a given DAG run, but does not provide explicit guidance on when to use it versus alternatives (e.g., airflow-get-task-logs for logs, airflow-list-runs for runs). No when-not or context exclusions are mentioned.

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