set_dag_paused

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

Describes the effect (pause/unpause), default behavior of new DAGs, and consequence of triggering while paused. It also mentions the return value (DagInfo). With no annotations, this provides sufficient behavioral insight for a simple toggle tool.

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 concise with no wasted words. It follows a logical structure: purpose, context, parameter docs, return value. Information is front-loaded.

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?

For a simple pause/unpause tool with output schema, this description is complete. It explains default behavior, interaction with triggering, and return format. No gaps identified.

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?

Despite 0% schema coverage, the description explicitly documents both parameters: 'dag_id: DAG identifier' and 'paused: True to pause, False to unpause.' This adds meaning beyond the schema's type and title, clarifying the boolean's semantics.

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 first sentence clearly states 'Pause or unpause a DAG.', using a specific verb and resource. It distinguishes from sibling tools like trigger_dag by focusing on state management.

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?

Provides context: newly added DAGs are paused by default, so trigger_dag will queue a run that never executes until unpaused. This guides when to call with paused=False to enable the DAG. While alternatives are implied, it doesn't explicitly state when not to use this tool.

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