create_a_flow_execution

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

The description adds non-idempotency detail beyond annotations (idempotentHint=false). However, it doesn't mention required permissions, rate limits, or what happens to existing data beyond creation.

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 has redundancy (repeats 'Create a Flow Execution') and includes a noisy icon and endpoint line. It's short but could be more concise and 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?

Given the complexity (nested objects, no output schema), the description lacks crucial details about return values, error handling, or post-creation effects. More completeness needed.

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%, so baseline 3. The description does not add any parameter meaning beyond what the schema already provides.

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 Flow Execution and notes non-idempotency. However, it repeats 'Create a Flow Execution' and doesn't explain what a Flow Execution is, which could be confusing among many create tools.

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 no guidance on when to use this tool versus alternative create tools (e.g., create_a_new_contact, create_broadcast). It lacks context for selection.

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