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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds meaningful context beyond them: the four possible verdict categories and the critical caveat that absence from the list must not be reported as allowed. It stops short of saying how the verdict is returned (state only vs. rule text), which leaves a small gap for a tool with no output schema.

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?

Front-loaded with the action and scope, then the trigger, then the caveat — a sensible order with no filler. The parenthetical example list in Ukrainian is slightly redundant with the schema examples, but it earns its place by anchoring the trigger condition.

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 two-parameter read-only lookup with a high-coverage schema, the description supplies purpose, trigger, result categories, and the not-found safety rule — essentially everything needed to call it and interpret it. Only the precise shape of the returned verdict is left implicit, which is a minor gap given no output schema exists.

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 schema already documents both 'item' (with its own examples) and 'lang' (enum, default). The description's item examples largely duplicate the schema and it says nothing about the lang parameter, so it adds only marginal meaning beyond structured fields — the baseline 3 applies.

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 and resource: 'Check whether an item can be shipped to/from Ukraine with SEMERO', and names the basis (SEMERO's published rules). The enumerated outcome states (prohibited, needs approval, not shipped by SEMERO, usually allowed) make it trivially distinguishable from siblings like delivery_rules or check_customs.

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?

Gives an explicit trigger: 'Use when the user asks whether a specific item can be sent', with concrete Ukrainian examples. It also gives a when-NOT-to-conclude rule ('If the item is not in the list, do not say it is allowed — a broker check is needed'), though it points to a human broker rather than naming the sibling tool that should be called instead.

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