ezd_pracownik_delete

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

The annotation already provides destructiveHint=true, and the description merely restates the deletion in words. It does not disclose whether deletion is permanent, whether it cascades to related records, what permissions are required, or whether it is a soft or hard delete.

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, efficient sentence with no filler and the core purpose front-loaded. It is appropriately short, though it sacrifices potentially useful operational context.

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 description is incomplete: it does not explain how the target employee is identified, what the response will look like, or what practical consequences deletion has. The optional parameters and their role in selecting the record are left unexplained.

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%, so the baseline is 3. The description adds no parameter-level meaning; the schema descriptions cover CID and the owner IDs, but the lack of an explicit target employee ID remains slightly confusing and is not clarified by the description.

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 ('Usun' – delete) on a specific resource ('pracownika' – employee) within the EZD PUW system. It is unambiguous as a delete operation, though it does not differentiate itself from the similar sibling 'ezd_api1_delete_worker'.

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 on when to use this tool versus alternatives such as 'ezd_pracownik_update', 'ezd_pracownik_transfer', or the legacy 'ezd_api1_delete_worker'. No conditions, prerequisites, or exclusions are mentioned.

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