Create a workflow

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false), so the bar is lower. The description adds genuine extra context: authentication is required, names must be unique per namespace, and a duplicate name yields a 400 validation error. It omits that the 'confirm' flag must be true for the mutation and that payload/payload_file/flat body are mutually exclusive, so not a full 5.

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?

Front-loaded with the core action, then organized under bold headers for auth, use cases, and the uniqueness caveat. Every section carries some signal, though the use-case bullets are the weakest and could be trimmed.

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 create tool with nested payload objects, no output schema, and annotations covering the safety profile, the description supplies the two things an agent most needs beyond the schema: auth requirement and the duplicate-name failure mode. Nothing critical to correct invocation 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 schema already documents all 8 parameters including the uniqueness constraint on 'name'. The description's uniqueness note only restates what the schema already says, adding no new syntax or format detail beyond the baseline.

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 new workflow') and identifies ownership ('owned by the authenticated user'). It is distinguishable from list_workflows/get_workflow by the create verb, but it never names or contrasts those siblings explicitly, so it falls short of a 5.

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 'Common Use Cases' section gives implied context (saving a built workflow, programmatic provisioning), but there is no explicit when-to-use-vs-alternative guidance and no when-not-to-use exclusions. 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.