BPMN-MCP

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

With no annotations provided, the description carries full burden but lacks behavioral details. It states the action 'connect' but doesn't disclose if this is a mutation (likely yes), what permissions are needed, if it's reversible, error conditions, or how it affects the diagram. This leaves significant gaps for a tool that modifies BPMN diagrams.

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 a single, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded with the core action.

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 complexity of a diagram mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after connection (e.g., diagram update, return values), potential side effects, or error handling, making it inadequate for safe and effective use by an AI agent.

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 schema description coverage is 100%, so the schema already documents all parameters (diagramId, sourceElementId, targetElementId, label). The description adds no additional meaning beyond implying the parameters are used for connecting elements, which aligns with the schema but doesn't provide extra context like format examples or constraints.

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 verb 'connect' and resource 'two BPMN elements with a sequence flow', which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'add_bpmn_element' or 'list_bpmn_elements', which might involve element manipulation but not specifically connections.

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. It doesn't mention prerequisites (e.g., needing existing elements or diagrams), exclusions, or how it relates to siblings like 'add_bpmn_element' for adding elements before connecting them.

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