workflow_restart_workflow

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

No annotations are provided, so the description carries full burden. It mentions creating a new execution but does not disclose what happens to the original execution (e.g., status change, termination). Side effects and permission requirements are missing.

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?

Two sentences plus concise bullet-style Args. Front-loaded with the main purpose. Every sentence is necessary and no fluff.

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?

Output schema exists but not shown; description covers basic purpose and parameters. However, it lacks behavioral context (e.g., idempotency, effect on original execution) which is important for a restart action. Not fully complete given the tool's complexity and absence of annotations.

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 description coverage is 0%, so the description adds value by explaining both parameters: workflow_id as 'The uuid representing the execution' and use_latest_definitions as 'If True, use the latest workflow definition instead of the original version'. Brief but sufficient.

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 verb 'Restarts' and the resource 'workflow execution', and specifies it creates a new execution with the same input. It distinguishes from siblings like retry (which resumes from failure) and resume (from pause).

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 implies usage by stating it restarts from the beginning and creates a new execution with the same input, but does not explicitly state when to use this tool versus alternatives like retry or resume. No exclusions or comparisons are provided.

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