create_flow

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

No annotations are provided, so description must carry full burden. It states 'Create a new blank flow' but does not disclose whether this requires specific permissions, whether it replaces any existing active target, or what happens if parameters are invalid. It also omits mention of the two trigger types defined in the schema.

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?

Description is a single sentence of 13 words, making it concise. However, it is overly terse and omits critical information about parameters and usage. Conciseness should not come at the expense of completeness.

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 tool has 2 parameters (one required, one optional enum), no output schema, and no annotations, the description is insufficient. It fails to explain parameter semantics, usage context, or behavioral expectations, leaving the agent under-informed for correct invocation.

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%, so description must compensate for missing parameter documentation. However, the description does not mention either 'displayName' or 'triggerType' at all, leaving their purpose and acceptable values entirely unexplained.

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?

Description clearly states verb 'Create' and resource 'blank flow', and specifies additional action 'connect it as the active target'. This distinguishes it from sibling tools like 'create_flow_in_solution' (which creates in a solution) and 'connect_flow' (which likely only connects an existing flow).

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?

Description provides no guidance on when to use this tool versus alternatives. For example, it does not mention that to create a flow in a specific solution one should use 'create_flow_in_solution', or that to clone an existing flow one should use 'clone_flow'. No when-not-to-use or prerequisites are indicated.

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