saved_workflow

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

With no annotations, the description is the sole source of behavior, and it does disclose two genuinely useful traits: save validates all steps before atomic storage, and saved workflows survive MCP restarts. It says nothing about whether delete is recoverable, what run returns, whether concurrent runs are allowed, or what happens on a name conflict.

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 compact sentences, front-loaded with the resource and operation vocabulary before the behavioral detail about validation and persistence. No filler, though the action list could be formatted more scannably.

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?

The heavy nested Workflow/WorkflowStep/Selector schema carries the bulk of the structural contract and an output schema exists, so the description only needs to frame the operations and key behaviors, which it largely does. The gap is per-action parameter requirements and the overlap with the run_workflow siblings.

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 coverage is 0% and the action parameter is a bare string with no enum, so the list of action values in the description is doing essential work the schema does not. However, it does not explain how name and workflow must be supplied per action (e.g. that save requires a workflow, load/run/delete require a name), leaving the caller to infer the per-action contract.

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?

"Persist/reuse named workflows" states a concrete verb and resource, and the list/save/load/run/delete enumeration makes the multi-operation nature explicit. It does not distinguish itself from siblings like run_workflow or workflow_control, which appear to overlap on the run capability, so an agent cannot tell from the description alone which to pick.

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 action names imply what the tool can do but there is no guidance on when to persist a workflow here versus executing it via run_workflow, workflow_control, or batch_ui_actions. No prerequisites, no mention of when a workflow should be saved at all or what a name collision means.

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