ds_rerun_from_failure

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

The description discloses a key behavioral trait: it reruns only failed/pending tasks and skips succeeded ones. With no annotations, this is valuable, but it doesn't mention side effects, permissions, or whether the original process instance is mutated.

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 a single, front-loaded sentence that conveys the tool's purpose and behavior with no unnecessary words. Perfectly concise.

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 tool with two primitive parameters and no output schema, the description is adequate for selection, but it lacks information about return values, error conditions, or side effects beyond the selective rerun behavior.

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?

The schema has 0% description coverage, and the description does not mention the parameters at all. The parameter names are somewhat self-explanatory, but the description fails to compensate for the missing schema details.

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 uses a specific verb ('resume') and clarifies the scope: rerun only failed and pending tasks, skip succeeded ones. This distinguishes it from sibling tools like ds_rerun_process_instance, which would rerun the entire process.

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?

It implies usage for recovering from failed tasks, and the parenthetical clarifies the selective behavior. However, it doesn't explicitly name alternative tools or when-not-to-use scenarios, so it's clear but lacks explicit exclusions.

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