ezd_api1_create_case_form

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

Annotations are absent, so the description carries the full behavioral burden. It states only that a form is created, but it does not disclose side effects, preconditions, permission requirements, defaulting behavior, or reversibility. 'Utworz' suggests mutation but adds little beyond the tool 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?

The description is a single sentence with no unnecessary filler and the action is front-loaded. It is compact, though so terse that it leaves behavioral and contextual details unstated.

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 mutation tool with no annotations and no output schema, one sentence is insufficient. It leaves unclear what entity the created form attaches to, what the API returns, and what preconditions apply (e.g., that the case cover must already exist).

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%, and each parameter has a description in the input schema, so the baseline is 3. The description adds no additional parameter-level meaning; all relevant semantics are already present in the schema.

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 uses a clear verb ('Utworz'/'create') and identifies a specific resource ('formularz koszulki sprawy' — case cover form) plus the API context ('przez API1'). However, it does not differentiate from the sibling tool ezd_formularz_create_case_form or other related create/update tools, so it doesn't full reach a 5.

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 when-to-use or when-not-to-use guidance is provided. It does not mention prerequisites (e.g., an existing IdKoszulki) nor contrast with the sibling ezd_formularz_create_case_form, leaving the agent to infer the appropriate context from the name.

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