Workflows: seed

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond that: it does not say whether seeding is idempotent, what happens if the workflow already exists, whether existing steps are replaced, or how {{KEY}} substitution failures are handled.

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?

A single front-loaded sentence with no wasted words. It is efficient, though arguably too terse for a mutation tool with three parameters.

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?

Annotations cover the mutation safety profile and the schema fully documents parameters, so the core is covered. But for a create/seed operation the description omits overwrite/idempotency behavior and sibling differentiation, which an agent needs to call it confidently versus workflows_create.

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% (var substitution, file path, enabled override all documented in the schema), so the baseline is 3. The description contributes nothing beyond the schema about parameter meaning or interaction.

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+resource ('Create a workflow and its steps') plus the input source ('from a JSON file'), which is more than a restatement of the name. It does not, however, explicitly set itself apart from the sibling workflows_create, leaving the agent to infer the distinction.

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 'from a JSON file' phrasing implies usage (when you already have an exported definition), and the schema hints at pairing with workflows export, but the description never states when to prefer this over workflows_create or workflows_step_add. Usage is implied rather than stated.

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