assign_receipt_to_transaction

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

With no annotations provided, the description carries full blame for behavioral disclosure. While 'zuordnen (Matching)' implies a state-changing link operation, the description doesn't clarify whether the operation overwrites existing assignments, whether it's idempotent, whether it validates that the transaction is a bank transaction, or what happens on failure. The api_key parameter hints at auth requirements but this isn't disclosed as behavior.

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, efficiently worded German sentence that front-loads the action verb and communicates the core operation immediately. Zero wasted words. It loses one point because it borders on being terser than necessary — the parenthetical is the only added flourish.

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 state-changing pairing tool with no output schema and no annotations, the description fails to mention whether the operation errors on already-assigned receipts, what it returns (the transaction? the assignment?), or whether it's part of a two-step match/unmatch flow (though the sibling unassign tool implies this). The absence of behavioral notes on idempotency or error cases makes this underspecified for a mutation operation.

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%, so the schema already documents all 3 parameters (api_key, receipt_id_by_customer, transaction_id_by_customer) with German descriptions. The description's noun phrases map conceptually to the params (Beleg→receipt_id, Banktransaktion→transaction_id), but it doesn't add format or constraint details beyond the schema. Baseline of 3 is appropriate per the rubric given high schema coverage.

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+resource pairing ('Ordnet einen Beleg einer Banktransaktion zu') that clearly identifies the operation as assigning a receipt to a bank transaction. The parenthetical '(Matching)' adds domain context. While it doesn't name sibling tools, the operation is specific and distinguishable from alternatives like unassign_receipt_from_transaction, though one point is lost for not being fully specific about which entity receives the assignment.

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 on when to use this tool versus alternatives. There is no mention of when to prefer unassign_receipt_from_transaction, what prerequisite state the transaction or receipt should be in, or when matching is appropriate. The only implied usage context comes from the tool name and sibling list, not from the description itself.

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