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

With no annotations, the description carries the full behavioral burden and does meaningful work: it discloses the tool is free, that output is a non-executing DRAFT, that nothing runs until publish, and that run_flow requires the Studio plan. It omits auth/permission requirements and failure behavior, but the side-effect profile (nothing runs) is the crucial disclosure for a create tool and it is present.

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?

Two sentences, front-loaded with the core action and the zero-cost fact, with the draft/publish constraint placed where it matters. It is dense rather than wasteful, though the long mid-sentence list of trigger types and engines makes the first sentence heavy.

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 no annotations and no output schema, the definition covers the essential facts an agent needs: what it makes, that the result is a draft, and how execution happens. It does not state the return value (e.g. a flow id) or auth needs, but the behavioral and routing information is otherwise sufficient.

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 baseline is 3, but the description adds real meaning beyond the schema by telling the agent what the 'description' parameter should contain — trigger, steps in order, engines (Clap, Claude/GPT/Gemini/Grok), formats, folders, platforms — and by enumerating the four trigger types the flow can start from. This goes past the schema's terse field definitions.

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 and resource — 'Build a new eroq Flow' — and enumerates exactly what the flow is composed of (start trigger, renders, writing steps, folder, post). It also differentiates from siblings by naming run_flow as the way to execute it, so an agent can tell it apart from edit_flow and run_flow without opening either schema.

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?

Gives clear context for use: it creates a DRAFT that does not run until published in the studio, and points to run_flow (Studio plan) as the execution path, which routes the agent between creation and running. It stops short of an explicit 'do not use this when...' or a direct comparison to edit_flow, so it is strong on context but lacks stated exclusions.

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