Create Workflow

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write/duplicate-on-retry profile is covered. The description adds nothing beyond that — no mention of required permissions, validation behavior, or what happens to the nested trigger_params configuration.

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 a single short sentence with no filler, so there is nothing to trim, but it is under-specified rather than concise — brevity here comes at the cost of all useful content.

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 tool whose schema contains deeply nested trigger configurations (action_item, alert, pulse, simple) and dozens of behavioral flags, one tautological sentence is grossly inadequate. An output schema exists, so return values need not be explained, but the input side is entirely unexplained.

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?

The single parameter is an opaque `data` envelope whose top-level structure (type='workflows' plus attributes) is undocumented in the description; 'from provided data' merely echoes the parameter name. The nested schema does describe many attributes, but the description adds no meaning about the envelope, required fields, or the trigger_params union that dominates the payload.

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 description restates the tool name and title almost verbatim: 'Creates a new workflow from provided data' adds only the words 'from provided data' beyond what the name already says. It does not distinguish this from the many sibling creation tools (create_workflow_task, create_workflow_group, create_workflow_run) or from update_workflow.

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?

There is no guidance on when to use this versus update_workflow or the other workflow-creation siblings, no prerequisites, and no mention of what a caller must know before creating a workflow. The agent is left to infer everything from the name.

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