List codelists

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds the domain clarification that codelists are 'independent option lists' scoped to a classification, but says nothing about pagination, ordering, or auth needs. With an output schema present, return format need not be described, so a 3 is appropriate.

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 front-loaded sentence with the scope stated first and the sequencing hint last; no wasted words. It is arguably too terse for the gaps it leaves, but as a structure it is efficient.

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 one-parameter read-only listing tool with a full annotation set and an output schema, the description covers the essential who/what/scope. The main remaining gap is that classification_id's accepted format is documented nowhere in either the schema or the description.

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% for the single parameter, so the description must carry the load. 'Within a classification' does establish that classification_id scopes the listing, but it gives no format, valid values, or source for the id. Partial compensation, not full.

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 ('List') and resource ('independent option lists within a classification'), which an agent can separate from list_classifications (classifications) and export_choice_list (exporting). The term 'codelists' is rephrased as 'independent option lists', which adds domain meaning. It stops short of naming the sibling it is not, so differentiation is inferable rather than explicit.

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 'before searching or exporting one list' gives an implied precondition for calling this tool, which is more than nothing. However, it never names the alternatives (search_codes, export_choice_list) or states when this tool should be skipped, so the routing is left to inference.

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