lemma_get_book_transfer

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

There are no annotations, so the description carries the burden of conveying behavior; 'Get' and 'by ID' communicate a read-only, single-record lookup with no side effects. It does not disclose not-found behavior, authorization needs, or return shape.

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?

One short, front-loaded sentence contains only essential information: action, resource, cardinality, and lookup key. There is no filler or redundancy.

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 one-parameter getter with no output schema, the description communicates the core call shape completely: provide a book transfer ID and receive that transfer. Minor gaps such as error behavior and exact return fields are secondary at this complexity.

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 0%, but the single parameter is self-descriptive and the description reinforces that it is the identifier for the lookup. It adds little beyond the schema's required book_transfer_id property, though the low parameter count limits the risk.

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 names a specific verb ('Get'), a specific resource ('internal book transfer'), and a retrieval scope ('by ID'). This distinguishes it from sibling tools like lemma_get_transaction and lemma_get_inbound_ach_transfer, which target different resources.

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 phrase 'by ID' implies the tool should be used when the agent already has a book_transfer_id and needs a single record. However, it gives no explicit guidance about when to prefer this over related getters or when not to use it.

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