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

Annotations only cover the safety profile (readOnly false, destructive false, idempotent false, openWorld true); the description adds substantive behavior beyond them. It discloses that static validation runs BEFORE the write, that a failed validation creates no version and returns findings (valid=false), that a new version is minted from the latest as an unpublished draft unless publish=true, and that base64+sha256 guards against corrupted or altered payloads.

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?

It is long, but front-loaded with the core purpose and every paragraph carries actionable content. There is some redundancy — the corruption rationale for base64 is explained twice — which keeps it just short of a 5.

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?

For a mutation tool with an output schema, the description covers what an agent needs: validation semantics, version-minting behavior, the publish flag, the staleness guard, and how to verify the result (run_workflow / preview the draft). Nothing operational is missing.

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 100%, so the baseline is 3 and the schema already carries the per-parameter detail. The description's mentions of replace_in, value_encoding=base64/gzip+base64 and value_sha256 largely restate what the schema fields already say, though it does add the decision rationale for choosing between them.

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 first sentence states a specific verb, resource and scope: editing an EXISTING workflow's latest version in place without resending the whole definition. The closing sentence explicitly names the sibling it is not (create_workflow_version for wholesale rewrites), so an agent can route between them without opening either schema.

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?

It gives explicit when-to-use rules with alternatives: replace_in for a small change to a large value, set with base64 for a large new value, create_workflow_version for a rewrite, and patch-then-preview instead of a separate preview step. The publish=true / draft distinction is also spelled out.

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