list_task_instances

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

No annotations provided, so description carries full burden. Explains wildcard query behavior (omitting params queries across all DAGs/runs) and time-filtering logic. Missing safety/performance warnings about expensive cross-DAG queries, but clear on pagination and defaults.

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?

Well-structured with purpose front-loaded, followed by Args, Returns, and Example. Args section is repetitive but necessary given zero schema coverage. Concrete example with inline comments adds value without verbosity.

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?

Excellent coverage for complex query tool: purpose, wildcards, all 16 parameters, return type (briefly acceptable since output schema exists), and working example. Complete despite no annotations and zero schema descriptions.

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 Args section comprehensively documents all 16 parameters including semantics (e.g., 'Filter by DAG ID (optional - omit for all DAGs)') and format hints ('ISO format'). Fully compensates for schema gaps.

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?

States specific verb 'List' with resource 'task instances across DAGs' and key capability 'flexible time-based filtering'. Distinguishes from sibling 'get_task_instance' by emphasizing plural listing and cross-DAG queries.

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?

Clearly states 'key tool for finding what tasks were running during a specific time window' and explains wildcard behavior (omit dag_id/dag_run_id to query across all). Includes concrete code example. Lacks explicit 'when not to use' or named sibling alternatives.

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