List Enumerations

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

No annotations are provided, so the description carries the full burden. It usefully discloses the exact count (26), the ADIF-vs-derived composition, and that each entry carries a ``source`` discriminator — real behavioral context. It stops short of stating read-only/permission characteristics or how the list is ordered, though the presence of an output schema reduces the need to explain 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?

Two tight sentences, front-loaded with the count and composition, followed by the one non-obvious semantic detail (the ``source`` field). 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 no-argument enumeration list with an output schema already documenting the return shape, this is nearly complete: scope, count, and the meaning of the ``source`` field are all covered. The only gap is the unstated relationship to search_enumerations.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate.

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?

States a specific verb ('Lists') and resource ('the 26 enumerations') with exact scope (ADIF 3.1.7's 25 plus Country). It does not, however, differentiate itself from the sibling search_enumerations, leaving the agent to infer that this is the full-list variant.

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 clause 'so a consumer loading reference tables can tell them apart' implies the intended use case (bulk reference-table loading), but there is no explicit when-to-use vs. when-to-use-search_enumerations guidance and no exclusions.

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