create_item_flow

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a mutation (create) and imposes a constraint, but does not mention potential side effects, permission requirements, reversibility, or failure behavior. The existence of an output schema is not reflected, and no return details are disclosed.

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 extremely concise: two short sentences with no redundancy. It front-loads the primary purpose and immediately follows with a key constraint. Every word earns its place, making it easy to parse.

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's context (a creation operation among many similar create_* tools), the description is too sparse. It does not explain what an ItemFlow is, how it relates to the connector, what the name parameter is for, or any constraints on connector_id. The output schema exists but is not described, and the description fails to provide sufficient guidance for an agent to call the tool correctly without additional inference.

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 0%, so the description must explain all parameters. It only addresses item_element_id by stating it must be a Classifier. It omits any clarification for connector_id and name, leaving those parameters undefined beyond their schema titles. The description adds minimal value and does not compensate for the lack of schema documentation.

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) and resource (ItemFlow on an existing Connector), which is specific and distinct from other flow-creation tools. It also adds a constraint on item_element_id, adding precision. However, it does not explicitly differentiate from siblings like create_control_flow or create_object_flow beyond the name.

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 alternatives such as create_control_flow or create_object_flow. It only states a prerequisite (item_element_id must be a Classifier), which is a constraint rather than usage context. No exclusions or alternative recommendations are given.

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