list_tnved_codes

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 describes the tool as a 'lookup' but does not disclose behavioral traits such as pagination behavior, rate limits, or error handling. The note adds scope context but not behavior.

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 sentences: the first states the purpose, the second adds critical usage context. Every sentence earns its place with no wasted words.

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?

Given that an output schema exists, the description does not need to explain return values. The description is complete for a lookup tool with well-documented schema parameters. Minor gap: could mention pagination behavior, but schema implies it.

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 coverage is 100%, so the baseline is 3. The description adds a scope context (linkage) but does not add additional meaning beyond what the schema already provides for parameters like page, query, prefix, and page_size.

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 clearly states 'TN VED EAEU classifier lookup' with a specific verb ('lookup') and resource ('TN VED codes'). The note about linkage distinguishes it from sibling tools that might involve different code types.

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 note explicitly clarifies that TN VED codes are linked only to certificates/declarations, not to vehicle type approvals or safety reports. This provides clear context on when to use this tool and when not, though alternative tools are not named.

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