ezd_pracownik_get_workflow_templates

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

Annotations declare readOnlyHint=true, and the description's 'Pobierz' is consistent with a read-only fetch. The description adds no extra behavioral context beyond the scope (assigned to employee), but there is no contradiction. With annotations covering safety, this is acceptable.

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?

A single concise sentence with no filler. The key action and object are front-loaded.

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 read-only list operation with optional params, the description covers the purpose but does not describe return values, and there is no output schema. It leaves the agent to infer that a list of template objects is returned, which is a minor gap.

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 input schema already documents CID, IdPracownikaWlasciciela, and IdStanowiskaWlasciciela with their defaults. The description adds no parameter-specific meaning beyond the schema, which is the baseline 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 Polish description 'Pobierz szablony obiegu dokumentow przypisane do pracownika' clearly states a specific verb (Pobierz/get) and resource (workflow templates assigned to a worker), which distinguishes it from siblings like the generic ezd_api1_get_workflow_templates.

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 implies the use case: retrieving templates assigned to a specific employee. However, it gives no explicit guidance on when to choose this tool over the nearly identical sibling ezd_api1_get_workflow_templates, nor any exclusions.

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