batch_bpmn_operations

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

Goes well beyond the sparse annotations (readOnlyHint=false, openWorldHint=false) by disclosing sequential execution order, the stop-on-first-error default, the opt-out flag, and the transactional rollback mechanism via the bpmn-js command stack — exactly the failure semantics an agent needs before batching writes.

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?

Four short sentences, zero filler, with the core purpose front-loaded and the execution/rollback semantics following in priority order. Every sentence carries distinct information.

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?

Covers invocation and failure semantics well for a mutation tool with no output schema, but is silent on the response shape — e.g. whether per-operation results/errors are returned and what a partial run looks like when stopOnError is false.

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 the baseline is 3, but the description adds real meaning the schema does not: stopOnError's default value and, critically, that rollback behavior is tied to it, which changes how an agent should set the flag.

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?

States a specific verb and resource ('Execute multiple BPMN operations in a single call') plus the benefit (reducing round-trips), which cleanly distinguishes this meta-tool from the individual operation siblings like add_bpmn_elements or connect_bpmn_elements.

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?

Gives a clear context for use (batching multiple operations to cut round-trips) and an explicit constraint ('Nested batch calls are not allowed'), but never states when to prefer individual calls over batching or any prerequisites/call-order limits.

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