ezd_api1_create_worker

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 states that the tool creates a worker; it does not mention authentication requirements, side effects, whether existing data is overwritten, or what response to expect. For a mutation tool, this is a significant transparency gap.

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 short sentence with no filler or repetition. It is efficiently worded and front-loaded with the action, though it is too sparse to provide broader 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 tool with 11 parameters, no output schema, and no annotations, the description is inadequate. It fails to explain which parameters are essential for a meaningful create operation, what the tool returns, or how API1 creation differs from other employee-creation tools in the sibling list.

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 all 11 parameters are already described with meaningful Polish labels. The description itself adds no parameter-level information, but the schema does the heavy lifting, meeting the baseline of 3.

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 and resource: 'Utwórz nowego pracownika' (create a new worker) through API1 in the EZD PUW system. While the verb is specific, it does not distinguish from the closely related sibling ezd_pracownik_add, which also appears to create an employee.

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 provides no guidance on when to use this tool instead of the many sibling tools, particularly ezd_pracownik_add, ezd_api1_update_worker, or 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.