list_dag_runs

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

Description mentions ordering behavior ('most recent first'), which adds value beyond the readOnlyHint annotation. However, it omits pagination details, limits, or any side effects; the annotation already declares read-only.

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?

Single sentence, very concise and front-loaded. However, for a tool with 5 parameters, it could provide a bit more high-level context without becoming verbose.

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?

Despite having output schema and annotations, the description is too brief for a tool with multiple filtering and pagination options. It does not explain filtering by state, limit/offset, or ordering beyond the default.

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 100% with descriptions for all 5 parameters. The description adds no extra parameter context beyond 'most recent first', which is implied by the default order_by. Baseline of 3 is appropriate.

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?

Description clearly states 'List runs of a DAG' with specific verb 'list' and resource 'runs of a DAG', and adds ordering 'most recent first'. It distinguishes from siblings like get_dag_run (single run) and list_dags (list DAGs).

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?

No explicit guidance on when to use this tool versus alternatives (e.g., get_dag_run for a single run). The context implies usage but lacks exclusions or prerequisites.

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