get_receipt

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

No annotations are provided, and the description does not explicitly state whether the operation is read-only or has side effects. It only mentions the optional file inclusion as Base64, but lacks details on error behavior, authentication requirements beyond the api_key parameter, or what happens if the receipt is not found.

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 concise sentence that directly states the tool's function without unnecessary words. It is well-structured and easy to understand.

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?

The description covers the basic action but lacks details on the return structure or expected output when get_file is not set. Given the simplicity of a get operation, this may be acceptable, but it leaves some ambiguity about what data is returned and under what conditions.

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?

The parameter descriptions in the schema already cover the meaning of id_by_customer and get_file. The tool description adds minimal extra context by linking id_by_customer to the receipt retrieval, but it does not significantly enhance understanding beyond what the schema already provides.

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 that the tool retrieves a single receipt by its id_by_customer, which is a specific action distinct from sibling tools like list_receipts or delete_receipt. The verb 'Ruft ab' (retrieves) and the object 'einen einzelnen Beleg' (a single receipt) make the purpose unambiguous.

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 usage for retrieving one specific receipt by ID, and the phrase 'einen einzelnen Beleg' indicates it is for a single receipt, providing sufficient guidance. However, it does not explicitly contrast with alternatives like list_receipts, which might return multiple receipts.

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