create_process_with_loops_and_multiinstance

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

No annotations are provided, so the description carries the full behavioral burden. It only offers a structural label (loops and multi-instance) and does not disclose side effects, input handling, permissions, output behavior, or whether anything is overwritten. This is a significant gap for a creation tool.

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 one short sentence with no wasted words. The qualifiers 'standard' and 'sequential/parallel' add useful detail without bloat. It is appropriately sized for the minimal information it conveys.

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 complex creation tool with no annotations, no output schema, and an undocumented parameter, the description is too thin. It does not cover input format, return value, prerequisites, or how it relates to the BPMN toolset. The sibling list offers context, but the description itself is incomplete.

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?

The sole parameter 'description' has 0% schema coverage and the description says nothing about it. The tool description does not explain what format or content is expected in 'description', so the agent must infer that it is a prose description of a process. The description fails to compensate for the schema gap.

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 names the process type (loops and multi-instance) and distinguishes it from similar tools like create_process_with_parallel or create_simple_linear_process. It lacks an explicit verb, relying on the tool name for the action, but the resource and scope are clear.

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?

No guidance is given on when to choose this tool over alternatives. There is no mention of use cases, exclusions, or conditions that would route an agent here instead of to a sibling like create_process_with_decision or create_subprocess.

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