ezd_formularz_create_case_form

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

No annotations are provided, and the description carries the full burden. It states the operation ('create') but does not disclose side effects, permissions, required context, or relationship to a case file/koszulka. It adds minimal context beyond the name.

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?

Single sentence with no filler. It is efficient, though very sparse; it communicates the core purpose without extra detail.

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 simple creation tool with 2 required parameters and no output schema, the description is minimally viable. However, no guidance on outputs, errors, or distinguishing from similar form-related tools leaves notable gaps.

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 schema already documents every parameter. The description adds no extra meaning about parameter semantics, such as how IdKoszulki relates to existing koszulka IDs or how NazwaFormularza is validated. Baseline 3 is appropriate due to full schema coverage.

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 says 'Utworz formularz koszulki sprawy w systemie EZD PUW' (Create a case file form in the EZD PUW system), naming a clear verb and resource. It distinguishes the tool as creating a form, though it does not explicitly name sibling alternatives like ezd_api1_create_case_form or ezd_formularz_set_view.

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 states what the tool does but gives no guidance on when to choose it over alternatives such as ezd_api1_create_case_form or ezd_formularz_set_view. With many similar siblings in the list, an agent would have to infer usage from the name and schema.

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