ezd_api1_delete_workflow_template

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

The destructiveHint annotation already communicates the destructive nature, and the description confirms the target object (employee workflow template). However, it does not disclose additional behavioral details such as irreversibility, cascading effects, or permission requirements.

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 sentence that clearly communicates the core action and object. The phrase 'przez API1 z systemu EZD PUW' is somewhat redundant given the tool name, but it does not significantly bloat the 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?

For a destructive tool with no output schema, the annotations and fully documented schema cover much of the operational context. Still, the description lacks guidance on deletion consequences, prerequisites, and which workflow template is selected when owner IDs are omitted, leaving some ambiguity.

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 already provides 100% description coverage for all three parameters, including defaults and the auto-generated correlation ID. The tool description adds no additional parameter-level meaning, so the baseline 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 the action ('Usun' = delete) and the specific resource ('szablon obiegu pracownika' = employee workflow template), and mentions the API path ('przez API1'). It distinguishes itself from sibling create/update/get_workflow_templates tools because it names deletion specifically.

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?

No guidance is provided on when to use this tool versus alternatives, no prerequisites are stated, and there is no indication of what conditions must hold before deletion. The intended use is only implied by the verb 'delete'.

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