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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the bar is lower. The description adds only the fact that the list is a fixed set of 45 entries, but gets behavior wrong by asserting it takes no input.

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 short sentences with no filler and the resource definition is front-loaded. The second sentence, however, is wasted space because it is inaccurate rather than informative.

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?

An output schema exists and the only parameter is documented in the schema, so not much more is required for a static reference list. Still, the description's incorrect claim about inputs and the absence of any statement of what the entries represent leave it only minimally adequate.

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% and the single 'fields' parameter is fully documented in the schema, so the baseline would be 3. However, the description states 'Takes no input', which is factually wrong and could lead an agent to omit the optional field projection entirely.

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 identifies the resource (the 45 Nice classes used for trademark filing), which is clearer than the name alone, but it largely restates the title and never says it returns the class number, heading and kind. It also offers no differentiation from sibling meta tools such as ud_get_meta_enums or ud_list_meta_datasets.

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?

There is no when-to-use guidance at all: no mention of using it to map a trademark class number to its heading, and no pointer to related tools. The only hint is the framing as a fixed reference list, which implies a lookup use case rather than stating one.

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