List Allowance Reason Codes

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

No annotations are present, so the description carries the behavioral disclosure burden. It communicates that the tool lists codes and identifies the code list source, but it does not explicitly state that the operation is read-only, whether it returns all codes, or whether the list depends on a particular code-list version. The 'List' verb makes the read-only nature reasonably inferable.

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 with no filler, repetition, or unnecessary details. Every word contributes meaning.

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 parameterless list tool with an output schema, the description is largely complete: it precisely identifies what is listed and from which standard. The only minor gap is that it does not mention code-list versioning or point to check_allowance_reason_code for single-code validation, but these are not required for correct invocation.

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 input schema has zero parameters and schema description coverage is 100%, so there is no parameter documentation burden for the description. The baseline for zero-parameter tools is 4, and the description adds relevant source context beyond the empty schema.

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 states a specific verb ('List'), a specific resource ('allowance reason codes'), and the source ('CEF EN 16931 code list'). This clearly differentiates it from sibling tools like check_allowance_reason_code (check vs. list) and list_charge_reason_codes (allowance vs. charge).

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 does not explicitly state when to use this tool versus alternatives, nor does it mention check_allowance_reason_code. However, the verb 'List' and the resource name imply the intended use case: retrieving the full set of allowance reason codes rather than validating a single code.

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