create_process_from_text_description

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

No annotations are provided, so the description carries the full burden of explaining behavior. It discloses only that the tool creates a BPMN process from a text description; it does not mention what the tool returns, whether a file is written, whether validation occurs, whether prior outputs are overwritten, or how the text description is supplied given the empty input schema.

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, front-loaded Spanish sentence with no filler. The core action, target artifact, and input source are all present in a compact and readable form.

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 empty schema, missing annotations, and lack of output schema, the description is too thin to fully support correct invocation. It does not explain how the textual description is passed to the tool, what kind of BPMN output to expect, or how to distinguish this from the many alternative creation tools in the sibling list.

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 input schema has zero parameters, so the baseline is 4. The description still adds meaning by naming the implicit primary input — a natural-language textual description — which is not represented anywhere in the schema. This helps the agent understand what conversational or contextual material is relevant.

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 a specific action ('Crea'), a clear resource ('un proceso BPMN'), and the distinctive input mode ('interpretando una descripción textual en lenguaje natural'). It clearly differentiates from image- or YAML-based creation tools, though it does not explicitly position itself against the many pattern-specific process-creation siblings.

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?

Usage is implied rather than stated: the agent can infer it should be used when a BPMN process needs to be generated from natural-language text. However, there is no explicit guidance about when not to use it or which sibling alternatives to choose for structured inputs, images, or specialized process patterns.

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