set_task_instances_state

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides none. 'Set a state' implies a mutation operation, but there's no information about permissions required, whether changes are destructive or reversible, rate limits, side effects, or what happens when state is changed. For a tool with 9 parameters that appears to modify workflow execution states, this lack of behavioral context is critically inadequate.

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 extremely concise at just 5 words, which is appropriate for its length. However, this conciseness comes at the cost of being severely under-specified rather than efficiently informative. The single sentence is front-loaded with the core action but lacks any supporting context that would make it genuinely helpful.

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 complexity (9 parameters, no output schema, no annotations, and multiple similar sibling tools), this description is completely inadequate. It fails to explain what the tool does beyond the obvious, provides no parameter guidance, offers no behavioral context, and gives no usage differentiation. For a state-modification tool in what appears to be a workflow/airflow system, this minimal description leaves the agent guessing about critical operational details.

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 and 9 parameters (7 optional), the description provides zero information about any parameters. It doesn't mention dag_id, state, task_ids, execution_date, or any of the boolean flags (include_upstream, include_downstream, etc.). The agent must rely entirely on parameter names without any semantic explanation of what these parameters mean or how they interact.

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 'Set a state of task instances' is essentially a tautology that restates the tool name with minor grammatical changes. While it indicates the verb ('set') and resource ('task instances'), it lacks specificity about what 'state' means or how this differs from similar tools like 'update_task_instance' or 'clear_task_instances' in the sibling list. The purpose is vague and doesn't provide meaningful differentiation.

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 provides absolutely no guidance on when to use this tool versus alternatives. With multiple sibling tools that manipulate task instances (clear_task_instances, update_task_instance, list_task_instances), the agent receives no indication of when this specific state-setting operation is appropriate versus other modification operations. There's no mention of prerequisites, typical use cases, or exclusions.

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