ezd_api1_set_form_view

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

There are no annotations, so the description bears the full burden. 'Ustaw' implies a state-changing operation, but the description does not disclose side effects, persistence, permissions, or what happens to the previous view, and no output schema exists to clarify the result.

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 action 'Ustaw widok formularza' is front-loaded. It loses one point for being too terse to carry the behavioral and usage context the tool needs.

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, and with a direct sibling that has almost the identical name, this one-sentence description is insufficient. The agent cannot determine when to invoke it, what the API1 distinction means, or what the call will return or change.

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 applies: the properties already document themselves. The description adds context that this is a form-view setter, but it adds no detail beyond the schema's parameter descriptions.

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: setting the form view via API1 in the EZD PUW system. However, it does not differentiate this tool from the near-identical sibling ezd_formularz_set_view, so it falls one point short of full clarity.

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 given about when to choose this tool over its alternatives. The phrase 'przez API1' hints at one implementation path, but there is no mention of ezd_formularz_set_view or of criteria such as API version or required worker context.

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