create_from_yaml_spec

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

No annotations are provided, so the description carries the full burden, but it only says it creates a BPMN process. It does not disclose whether the generated process is validated, written to a file, overwrites existing artifacts, or what the response contains.

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?

A single front-loaded sentence with no filler; every word contributes to the core purpose and source format. It is appropriately concise for a description.

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 no annotations, no output schema, one undocumented parameter, and many sibling tools, the description is too sparse. It lacks input format details, output expectations, and guidance for distinguishing it from similar creation tools.

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 0% and the single 'description' parameter has no type or explanation. The tool description mentions YAML/JSON specification but never explicitly connects it to the 'description' parameter, so the agent is left to infer how to pass the spec.

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 states a specific action ('Crea un proceso BPMN') and a distinct source format ('especificación YAML/JSON estructurada'), making it distinguishable from siblings such as create_process_from_text_description and create_process_from_image. Despite being in Spanish, the verb + resource + source combination is unambiguous.

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 source format implies the tool should be used when the user has a structured YAML/JSON specification, so there is some implied usage context. However, it does not explicitly state when to prefer this over the many sibling creation tools or provide any exclusions.

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