ezd_blockchain_get_last_record

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

The annotation readOnlyHint=true already covers the read-only safety profile. However, the description adds no behavioral context beyond the basic purpose: it does not explain how 'last' is determined, whether scoping by worker/position applies, or what the response represents.

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, direct sentence with no filler. The key scoping term 'ostatnie' appears immediately after the verb, and every word contributes to the basic meaning.

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?

Although the tool is simple and read-only, the description does not clarify what 'utrwalenie' means, whether the result is scoped to the worker/position context, or what an agent should expect as output. With no output schema and no discussion of alternatives, these gaps make the description incomplete for confident invocation and interpretation.

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 all three parameters (CID, IdPracownikaWlasciciela, IdStanowiskaWlasciciela) are already documented with their defaults. The description adds no parameter-level information, so the baseline of 3 is appropriate.

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 uses a specific verb 'Pobierz' (fetch) and a clear resource, 'ostatnie utrwalenie z blockchain' (last blockchain record) in the EZD PUW system. The word 'ostatnie' differentiates it from sibling ezd_blockchain_get_record, though it does not explicitly name that alternative.

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 use this tool instead of ezd_blockchain_get_record or ezd_blockchain_order_immutability. There are no conditions, exclusions, or alternatives mentioned, so an agent must infer usage from the tool name alone.

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