manage_bpmn_root_elements

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

Annotations declare readOnlyHint=false, idempotentHint=true, and openWorldHint=false, so the mutating-but-idempotent safety profile is already covered. The description adds genuine context beyond that: these are shared, cross-referenced definitions, implying a change can affect multiple event definitions. It does not, however, state update semantics (replace vs. merge) or what happens to omitted definitions.

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?

Two sentences, front-loaded with the action and resource, followed by the reference context. No filler; every clause earns its place.

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 mutation tool with no output schema and full schema coverage, the description supplies the needed purpose and reference semantics. It stops short of explaining update behavior for existing definitions or whether omitted arrays are left untouched, which would make it fully complete.

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 description coverage is 100%, so the schema already documents diagramId, messages, and signals with their id/name sub-fields. The description references messageRef/signalRef but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 pair (create or update) and precise resource (shared root-level bpmn:Message and bpmn:Signal definitions). This clearly distinguishes it from element-level siblings like add_bpmn_elements and even names set_bpmn_element_properties as the consumer of these definitions.

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 makes the use case clear: define shared message/signal objects that multiple event definitions reference. It names the sibling mechanism (messageRef/signalRef via set_bpmn_element_properties) that consumes them, giving strong routing context. It lacks an explicit when-not-to-use exclusion, so it falls short of a 5.

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