ezd_api1_create_workflow_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 only communicates that the tool creates something; it does not disclose permissions required, side effects, idempotency, or what happens on duplicate submissions.

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 concise sentence with no wasted words. The phrase 'przez API1' is slightly redundant with the tool name, but the overall structure is clean 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?

With no annotations and no output schema, the one-sentence description is insufficient for an agent to fully understand the operation's context. It does not describe return values, validation behavior, ownership defaults beyond the schema, or how this creation interacts with existing workflow templates.

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 description coverage is 100%, with each parameter already documented, including the default behavior for IdPracownikaWlasciciela and IdStanowiskaWlasciciela. The tool description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

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 a specific action: 'Utworz szablon obiegu pracownika' (create an employee workflow template) via API1. The create verb distinguishes it from sibling tools like ezd_api1_update_workflow_template and ezd_api1_delete_workflow_template, though it does not explicitly name those alternatives.

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 gives no guidance on when to use this tool instead of the related update/delete/get workflow template tools. It also does not mention prerequisites, such as whether the employee must already exist or what distinguishes a workflow template from a transfer-by-template operation.

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