create_workflow

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

Discloses key behaviors: step results auto-appended to payload, WEBHOOK can point to Slack, and free plan limitation. Since no annotations exist, the description carries the full burden and does so well.

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 core purpose, each sentence adds value. Slightly verbose in the middle but overall efficient and well-structured.

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?

Completely covers creation, alert mechanism, payload behavior, and constraints. No output schema necessitates description to explain return value implications (implicitly through payload description).

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 already covers 100% of parameters, so description adds value beyond schema by explaining how stopIfEmpty enables alerting and that step results are appended to 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 clearly states the tool creates a workflow with SQL steps and EMAIL/WEBHOOK actions, and supports manual or cron schedule. This distinguishes it from siblings like list_workflows or run_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?

Provides explicit guidance on how to create alerts using stopIfEmpty and mentions the free plan limit of 3 workflows. Could be improved by specifying when not to use this tool, but the alert pattern is well explained.

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