ezd_blockchain_get_record

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

Annotations already convey readOnlyHint=true, and the description aligns with that by saying 'Pobierz' rather than implying mutation. It adds some scope context by specifying the lookup by order identifier, but it does not disclose response behavior, error cases, or whether multiple records can match.

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 focused sentence with no filler. It is front-loaded with the action and resource, and every word contributes to identifying the tool's purpose.

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 lookup, the description provides the essential purpose and key input. However, with no output schema, the description does not explain what the returned 'utrwalenie' contains or how the caller should interpret the result, leaving a moderate 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 baseline applies. The description reinforces that IdZlecenia is the lookup key, but it does not add detail beyond what the schema already provides for each parameter.

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 ('Pobierz' / retrieve), a clear resource ('utrwalenie z blockchain'), and a precise lookup key ('po identyfikatorze zlecenia'). This distinguishes it from the sibling ezd_blockchain_get_last_record, which targets a different record selection.

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 this tool is for fetching a blockchain record by an order identifier, but it gives no comparison to ezd_blockchain_get_last_record or ezd_blockchain_order_immutability. It offers no explicit when-to-use or when-not-to-use guidance.

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