save_workflow

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

With no annotations the description must carry the behavioral burden; it does disclose the write target and that a path is returned. However it never addresses whether an existing file with the same name is overwritten, whether the directory is created, or what failures look like — the key risk for a file-writing mutation.

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?

Three tight sentences: action and destination first, return value second, lifecycle guidance last. No filler and nothing buried.

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 two-parameter tool with full schema documentation and a stated return value, the only missing piece is overwrite/idempotency behavior. Otherwise an agent has everything needed to call it correctly.

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 both parameters and the .json suffix rule are already documented in the schema. The description adds only the path pattern, which largely duplicates that, so baseline 3 applies.

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?

States a specific verb and resource ('Save a workflow JSON to file') plus the concrete destination pattern workflows/<name>.json, which lets an agent picture the effect. It is clearly a persistence step distinct from create_workflow/finalize_workflow, though those siblings are never named for contrast.

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?

'Use after build_workflow to persist for later load_workflow or execute_workflow' gives an explicit lifecycle position and names the follow-on tools. It does not say when to prefer this over create_workflow or finalize_workflow, which are the closest ambiguous alternatives.

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