run_saved_workflow

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this mutates state. The description adds nothing about what the replay actually touches, whether it is repeatable or idempotent, or what happens if the params do not match the saved workflow. For a destructive tool, that is a real gap.

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 short sentences, front-loaded with the action, and the second sentence adds a genuine usage hint rather than filler. Nothing is padded, though the brevity is partly the source of the missing detail.

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?

This is a destructive, nested-parameter tool with no output schema and no documented parameter meanings, so the description carries most of the burden and does not meet it. An agent would not know how to shape `params` or what a successful replay returns.

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% and the params object is a free-form nested object with no properties defined, so the schema explains almost nothing. The description says only "new parameter values", without saying that `name` identifies the saved workflow or how keys in `params` map to the saved workflow's parameters.

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?

"Replay a saved workflow with new parameter values" gives a specific verb (replay) and a specific resource (a previously saved workflow), which separates it from propose_workflow and save_workflow. It does not explicitly contrast with execute_workflow, so the differentiation is only implicit.

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 planning needed" implies this is the shortcut path that skips propose_workflow/planning, which is useful context. However, it never states when to prefer this over execute_workflow, nor any prerequisite such as the workflow having been saved first.

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