create_from_template

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 behavioral disclosure. It states the create action but omits side effects, where the BPMN file is written, whether process_name selects a template or names the output, and what the agent should expect after execution.

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 clear sentence with no filler, which is good for conciseness. However, it is so thin that it omits critical operational and parameter guidance, so the brevity comes at the expense of usefulness.

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?

With no annotations, no output schema, and a bare parameter schema, the description is insufficient for reliable invocation. It does not clarify how a template is selected, what process_name refers to, or what output to expect, and the agent would likely need to consult sibling tools like list_templates or get_template_details first.

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 one parameter, process_name, with 0% description coverage, and the tool description does not mention it at all. The phrase 'from a predefined template' does not explain what process_name means, how it maps to a template, or what format is expected, so the agent cannot determine how to populate the parameter.

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 Spanish description uses the verb 'crea' and identifies the resource as 'un proceso BPMN desde una plantilla predefinida', making the core function clear. It is somewhat distinguished from sibling creation tools by the 'predefined template' source, though it does not name specific templates or compare itself to create_from_yaml_spec.

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?

There is no guidance about when to use this tool versus alternatives such as create_simple_linear_process, create_process_with_decision, or create_from_yaml_spec. The only implicit signal is 'template', but no conditions, prerequisites, or exclusion criteria are stated.

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