lemma_list_remittances

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

With no annotations provided, the description carries the behavioral burden. It clearly signals a read-only list operation and lists the kind of data returned, which is adequate. However, it does not disclose pagination behavior, default ordering, or whether the 835 availability field is simply a boolean or implies something deeper, so some behavioral context is missing.

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 compact sentence that leads with the action and resource, then parenthetically lists the useful output fields. There is no redundant or filler content; every element earns its place.

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 tool has 7 parameters and no output schema, and the description provides only a high-level list of returned fields. The schema covers parameter semantics, but the description does not explain pagination flow, result ordering, or how this tool relates to get_remittance_era. It is minimally viable but leaves an agent to infer several operational details.

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 86%, so the input schema already explains limit, payer, cursor, updated_since, received_on_or_after, and received_on_or_before. The description adds no parameter-level meaning beyond naming the output fields. The required entity_id is left only as a property name, but that is acceptable given the 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 ('List') and a clear resource ('an entity's insurance remittances'), and it enumerates the returned fields (payer, payment amount, trace number, 835 ERA availability). It is not explicitly contrasted with siblings like lemma_get_remittance_era, but the list-versus-get distinction is apparent from the description.

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 states what the tool does but gives no guidance on when to choose it over related list tools such as lemma_list_check_deposits or lemma_list_transactions, nor does it mention prerequisite context such as needing an entity_id or how to obtain one. Usage must be inferred entirely from the tool name and purpose.

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