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

Beyond the destructiveHint=true/idempotentHint=true annotations, it discloses the two-phase confirm protocol: an unconfirmed call writes nothing and returns the diff plus an edit_token required by confirm=true. That is substantial behavioral context (dry-run semantics, token dependency) the annotations do not convey.

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?

Purpose is front-loaded in one sentence, followed by a tight procedural paragraph. Every sentence carries load (read source, validate, dry-run, then confirm), with no filler or repetition.

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 destructive, nested-object mutation with an output schema, the description covers the required pre-steps, the token chain, and the confirm safety gate, so an agent has everything needed to invoke it correctly. Return values are covered by the output schema.

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 100%, so the baseline is 3, but the description adds cross-parameter meaning by chaining the params: the edit_token comes from this tool's own unconfirmed reply and confirm=true requires it, and it clarifies what the confirm=false default does. This ties the individually-documented fields into a coherent flow.

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?

"Replace an existing workflow's graph with an edited definition" is a precise verb+resource+scope statement, so the agent knows this is a full-graph replacement rather than a mutation. It does not explicitly contrast with the sibling patch_workflow, so the replace-vs-patch distinction is left 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?

It lays out an explicit ordered workflow: read the current graph with get_workflow(include_definition=true), edit, then validate_workflow_definition for the token, then call without confirm first. The condition selecting the safe vs destructive call is spelled out, and alternative tools are named.

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