Create workflow

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

This goes well beyond annotations by disclosing that workflows run automatically against future documents and that a mistake can silently mis-file everything afterward. That is behavioral context an agent cannot infer from readOnlyHint or destructiveHint alone, and it appropriately raises the caution level for this mutation tool.

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 long but packed with necessary detail for two complex nested objects. It is front-loaded with the most important warning before diving into field semantics. Some content duplicates the input schema descriptions, and the '5=..., 6=...' placeholders are weak, but overall the length is justified.

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?

Given the complexity of trigger/action configuration and the lack of an output schema, the description covers the critical invocation concerns: what to build, how to model it, and what risks to consider. It does not describe the return value or what happens after successful creation, which is a minor gap for a create operation.

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 description substantially compensates for incomplete schema coverage by enumerating trigger types, source filters, schedule fields, action types, and action-specific assignment/removal fields. It loses one point because action types 5 and 6 are left as '...' and a few fields like matching_algorithm are named but not explained.

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 opens with a clear verb and resource: 'Create an automation rule.' It clearly identifies the workflow domain and is distinguishable from sibling tools like update_workflow, delete_workflow, and get_workflow. The mention of reading get_workflow to copy the shape reinforces what this tool is for.

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 description gives strong usage guidance: workflows act on future documents, mistakes are high-stakes because they silently mis-file, and the user should confirm the rule before creation. It also points to get_workflow as a way to model the correct shape, which is an explicit alternative/helper strategy.

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