pause_dag

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

With no annotations provided, the description carries full burden and thoroughly explains behavioral traits: no new scheduled runs, current tasks complete, manual triggers still possible, UI indicator, and that it's a write operation modifying state until unpaused.

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 front-loaded with the primary action and uses multiple paragraphs effectively. However, the list of user queries could be slightly trimmed without losing clarity.

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 simplicity of the tool (1 param, output schema present), the description fully covers the purpose, behavior, return value, and usage guidance. No missing aspects are apparent.

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 0%, but the description adds an 'Args' section with dag_id and an example value, providing context beyond the schema's type and required fields. While minimal, it adequately clarifies usage for the single parameter.

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 pauses a DAG to prevent new scheduled runs, providing a specific verb-resource pair. It lists example user queries like 'Pause DAG X' which distinguishes it from siblings like unpause_dag.

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 explicitly lists when to use this tool (e.g., user asks to pause, disable, turn off scheduling), making context clear. However, it does not explicitly exclude alternatives or mention when not to use, though the sibling unpause_dag is implied.

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