ezd_api3_register_document

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that the tool registers a document and accepts an attribute array, but it does not mention permissions, side effects, defaults for owner IDs, idempotence, or what the response contains.

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 two short sentences with the primary action front-loaded. It contains no filler or redundant explanation, making it easy for an agent to scan and act on.

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?

Despite a nested object and four parameters, there is no output schema and no annotations. The description omits important context such as CID behavior, owner ID defaults, and expected return values, leaving the agent with limited guidance for correct invocation.

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 structured schema already documents the parameters. The description adds a brief restatement of the attribute array shape ({Klucz, Typ, Wartosc}), which reinforces but does not materially extend the schema's meaning.

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 the action ('Zarejestruj nowy dokument w EZD PUW') and identifies the resource and the attribute structure. It does not, however, differentiate this tool from similar siblings like ezd_dokument_register or ezd_dokument_add, which may overlap in purpose.

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?

There is no guidance on when to use this tool versus alternatives such as ezd_dokument_register, ezd_dokument_add, or ezd_api3_register_inflow. The description tells how to pass attributes but does not state prerequisites, exclusions, or selection criteria.

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