describe_workflow

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

With no annotations, the description carries the full burden. It helpfully discloses node-type behavior, especially image_input, output, and rerolls_each_run seed behavior, but it does not state whether the operation is read-only, what happens if the workflow name is invalid, or any permission/error characteristics.

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 compact and front-loads the main return content before explaining special node behaviors. The first sentence is somewhat fragment-like, but each sentence provides useful information and there is little wasted text.

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?

An output schema exists, so the description is not required to fully explain return values. It adds useful node semantics, but it remains incomplete for an agent that needs to know when to use this tool and what the required 'name' parameter represents.

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 should compensate for the single 'name' parameter. It does not explain whether 'name' means workflow name, display name, ID, or where the caller should obtain it, leaving a meaningful gap despite the small parameter set.

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 that the tool exposes a saved workflow's nodes and editable values, including per-node id, title, class, and widget inputs. It does not name a sibling tool or explicitly contrast itself with list_workflows or run_workflow, so it stops short of full sibling differentiation.

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?

There is no explicit guidance on when to call this tool versus alternatives such as list_workflows or run_workflow. The mention of run_workflow images is a cross-reference for node semantics, not usage guidance for this tool.

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