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

With no annotations, the description carries the full behavioral burden and discloses API-key authentication, edition-aware/historical resolution, a five-target cap, cursor pagination, and the non-binding nature of results. It still does not explicitly state read-only behavior, side effects, or rate limits.

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?

The description is four compact sentences covering access, purpose, capabilities, and a caveat, with no repetition. It is mostly front-loaded, though the API-key note precedes the core purpose.

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?

This is a complex tool with 10 parameters, no annotations, no output schema, and very low schema description coverage. The description gives high-level capability but omits enough parameter and return-value detail that an agent cannot confidently know how to invoke it correctly.

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 only 10%, and the description helps by explaining as-of/history, editions, the five-target cap, pagination, and the country/system scope. It does not explain the required code/source/target relationship, include values, or limit/cursor semantics for most of the 10 parameters.

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 operation—finding edition-aware concordance candidates across China, US, EU, GB, and Brazil tariff systems—and the resource being compared. It implies cross-system comparison but does not explicitly contrast with siblings such as lookup_tariff or search_tariffs.

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 description implies use for cross-system concordance and notes candidates are non-binding classification leads, which is useful context. However, it never states when to use this tool instead of lookup_tariff/search_tariffs or when it is inappropriate.

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