create_flow

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

The description discloses that it creates a draft, validates fields, and returns the created flow with id and version. Without annotations, it covers key behavioral aspects, though it could mention validation failure behavior.

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 efficiently cover purpose, usage, and return value. No wasted words, front-loaded with main action.

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 one parameter and no output schema, the description adequately explains the input and output. It could note if fields are optional or if there are constraints, but it's mostly complete.

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 coverage is 100%, and the description adds value by specifying camelCase keys and providing an example (name, description), which goes beyond the schema's 'additionalProperties' object.

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 action 'Create a new flow draft' and the resource 'flow'. It distinguishes from sibling tools like list_flows, read_flow, update_flow, etc., by specifying that it creates a draft.

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 provides usage guidance by instructing to pass fields in camelCase and noting backend validation. However, it does not explicitly state when not to use or mention alternative tools like update_flow.

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