create_workflow

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

With no annotations provided, the description must carry the behavioral disclosure burden. 'Create a new workflow.' only states the basic action, but does not disclose any side effects, required permissions, default values (e.g., whether the workflow is enabled by default), or reversibility. The description offers minimal transparency beyond the inherent mutating nature of 'create.'

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?

The description is excessively short, consisting of only one sentence that restates the tool name. While it is technically concise, it under-specifies the tool's behavior and parameters. It does not front-load any helpful information beyond the literal action, making it more under-specification than effective conciseness.

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 with 3 parameters, no annotations, and no output schema, the description is wholly inadequate. It does not explain what a workflow is, what the parameters mean, or any constraints. The reliance on sibling tool names for context is insufficient because the description itself adds no value, leaving the agent with no understanding of how to invoke the tool 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 description coverage is 0%, and the description provides no information about the three parameters (name, enabled, description). The description does not compensate for the lack of schema descriptions, leaving the agent without any guidance on how to fill these fields correctly. This is a significant gap.

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 clearly states a specific verb and resource: 'Create a new workflow.' This uniquely identifies the operation as the create counterpart to sibling tools like update_workflow, delete_workflow, and get_workflow. The purpose is unambiguous and distinguishes the tool from its siblings by the action it performs.

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 tool versus alternatives. It does not mention that this should be used to create a new workflow, while update_workflow is for modifying existing ones, or that it may be a prerequisite for workflow steps. No context or exclusions are provided.

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