lemma_get_ach_transfer

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

With no annotations, the description carries the full behavioral burden. It clearly signals a read operation via 'Get', indicates a single-object result via 'one', and discloses the possible transfer statuses (pending/submitted/settled/returned/canceled/rejected), which is useful context beyond the tool name.

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?

A single efficient sentence communicates the action, resource, lookup key, and relevant statuses. Every element earns its place with no filler.

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 simple get-by-ID tool with one parameter and no output schema, the description covers the essential invocation context. The status list enriches the expected result context, though it does not specify the full return structure or error behavior, which would be useful but not critical.

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%, so the description must compensate. It only says 'by ID', which adds little meaning beyond the parameter name ach_transfer_id. It does not describe the ID format, where to find it, or any constraints on the value.

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 ('Get') and resource ('one outbound ACH transfer by ID'), immediately distinguishing it from siblings like lemma_get_inbound_ach_transfer. The status list adds further precision about what the tool handles.

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 this tool is for fetching a single transfer when an ID is known, and the 'outbound' qualifier distinguishes it from inbound-transfer siblings. However, there is no explicit guidance about when to prefer this over related tools such as lemma_get_transaction or lemma_list_inbound_ach_transfers.

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