undo_workflow_run

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

No annotations are provided, and the description only states the action without disclosing side effects, permissions, idempotency, or what happens to associated resources. The full behavioral burden falls on the description, which does not satisfy it.

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, focused sentence with no irrelevant information. It is appropriately brief for a simple one-parameter tool.

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?

While the tool is simple, the broader context is incomplete: it does not specify which workflow run states are valid, what the output contains, or how this operation differs from deleting workflow runs. The presence of an output schema makes the lack of output behavior information more noticeable.

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 only parameter run_id is self-explanatory from its name, but the description adds no additional meaning about the expected format, source, or how to obtain it. Since the schema has no description field, this minimal explanation leaves important details implicit.

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 a specific action and object: 'Annule un run de workflow' meaning 'Cancels a workflow run.' It is concise and identifies the tool's primary purpose, though it does not differentiate it from related operations like delete_workflow_runs.

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 guidance is provided about when to use this tool versus alternatives such as delete_workflow_runs or apply_workflow. There is no mention of whether the run must be in progress, whether cancellation is reversible, or any other contextual usage condition.

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