lemma_get_inbound_ach_transfer

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'Get' signals a safe, read-only retrieval, and 'by ID' clarifies the lookup mechanism. However, it does not disclose error behavior, authorization needs, or whether the ID is platform-specific vs external.

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, front-loaded sentence. Every word adds meaning: action, resource, cardinality, and lookup key. There is no filler, repetition, or unnecessary detail.

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?

This is a one-parameter, low-complexity read tool with no output schema or nested objects. The description states the operation and the required input clearly. Minor gaps like explicit not-found behavior or routing to the list sibling are not critical at this level of 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?

The schema provides only the parameter name and type, and schema description coverage is 0%. The description adds the key semantic that the ID identifies a single inbound ACH transfer. It does not provide format or source guidance, but the parameter is self-descriptive enough for basic use.

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 action ('Get'), a specific resource ('inbound ACH transfer'), and the lookup scope ('one... by ID'). This clearly distinguishes it from sibling tools like lemma_list_inbound_ach_transfers and lemma_get_ach_transfer.

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 wording clearly implies this is the single-record lookup tool: use it when you have an inbound ACH transfer ID. It does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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