Get receipt

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

Discloses error handling behavior (400 returns verbatim error, adjust fields and retry) and references API docs. No annotations provided, so description carries burden; covers key behavioral traits for a simple GET operation.

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?

Two concise sentences: first states core function, second adds essential error handling. No extraneous information, front-loaded structure.

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?

Tool is simple (1 param, no output schema), and description covers purpose, usage hint (retry on 400), and reference to field definitions. No missing critical context.

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% with a clear description of 'id'. The tool description adds minimal extra meaning ('single receipt', API docs reference), but this is sufficient given the schema already defines the parameter well.

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?

Description clearly states 'Get a single receipt by id', specifying the verb (get) and resource (receipt). It distinguishes from sibling tools like loyverse_list_receipt (list) and loyverse_create_receipt (create).

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 explicit guidance on when to use this tool versus alternatives. Implied that it's for fetching a specific receipt by ID, but no mention of when not to use or comparison to list/get siblings.

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