Create Integration Flow

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

With no annotations, the description bears full responsibility for behavioral disclosure. It adds that the flow is empty and version 1.0.0, but omits critical details like idempotency, error handling, or response format. The confirm parameter's requirement is already 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?

The description is concise with two sentences, front-loading the purpose and context without unnecessary words.

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 5 parameters, 3 required, no output schema, and no annotations, the description is too sparse. It omits explanations for the confirm safety guard, id format nuances, and post-creation steps beyond 'edit in web editor'.

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 40% (only id and confirm have descriptions). The description adds the ALLOW_WRITE requirement but does not clarify the meaning or format of packageId, name, or description, failing to compensate for low coverage.

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'), the resource ('integration flow'), and specific details ('empty', 'in a package', 'default flow at version 1.0.0'). It distinguishes itself from siblings like create_integration_package and save_integration_flow_as_version.

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 mentions the requirement for ALLOW_WRITE permission and implies usage when creating a new flow, but does not explicitly state when not to use or list alternative tools for editing or versioning.

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