ezd_api3_register_epuap

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

There are no annotations, so the description carries the full burden of disclosing side effects. 'Zarejestruj' implies a state-changing registration, but the description does not clarify whether the shipment is actually transmitted via ePUAP, what records are created or updated, or what response to expect. The stated requirements are preconditions, not behavioral outcomes.

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 one front-loaded action sentence plus a terse requirement clause, with no filler. It efficiently communicates the core action and prerequisites, though it sacrifices some behavioral context for brevity.

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?

With eight parameters, no annotations, and no output schema, this description is too sparse to fully orient an agent. It omits the required IdPracownika from its prose prerequisites and does not clarify the registration's effects or how it differs from neighboring ePUAP/e-delivery tools.

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 coverage is 100%, so the baseline applies. The description maps three conceptual prerequisites (adresat, skrytka ePUAP, dokument pisma) to core parameters, but adds no format, default, or relationship information beyond 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 specific verb ('Zarejestruj') and a clear resource ('wysylke przez ePUAP') with system scope ('w EZD PUW'). It distinguishes itself by naming the ePUAP shipment registration action, though it does not explicitly contrast with sibling registration tools like ezd_api3_register_edoreczenia.

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 phrase 'Wymaga adresata, skrytki ePUAP i dokumentu pisma' gives concrete prerequisites for using the tool. However, it does not explain when this tool should be preferred over alternatives such as ezd_api3_register_edoreczenia or ezd_api3_register_correspondence; usage is implied rather than explicit.

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