create_subprocess

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 reveals that the tool creates an embedded subprocess with internal activities, but it does not explain side effects, output behavior, required context, validation, or whether an existing process must be selected. This is thin behavioral coverage for a creation tool.

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 concise and starts with the action, but it is under-specified. There is no wasted wording, but the brevity comes at the cost of missing necessary context, so it is concise yet not well proportioned for the tool's actual complexity.

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 only a minimal schema, the description needed to provide substantially more operational context. It covers the core idea but omits how to invoke it, what the parameter should contain, and what happens after creation. The tool is not fully unspecified, but it is far from complete enough for reliable agent usage.

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 has a single property named 'description' with no type or description, and schema description coverage is 0%. The tool description never explains how to use the 'description' parameter, what kind of content it expects, or how it relates to the 'internal activities' mention. The parameter semantics are effectively undocumented.

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 clear action ('Crea') and a specific BPMN resource ('subproceso embebido') with a notable qualifier ('con actividades internas'), which helps distinguish it from sibling tools like create_simple_linear_process or create_call_activity_process. However, it does not explicitly contrast it with the many sibling creation tools, so it is clear but not fully differentiated.

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 choose this tool over the many sibling creation tools, no prerequisites, and no alternatives mentioned. The description only states what it does, leaving the agent to infer the appropriate usage context on its own.

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