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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and not contradicted. The description adds useful source context (TB-TCHQ notices) but says nothing about result limits, pagination, or what happens when no ruling matches, so it only modestly exceeds the annotation baseline.

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 the core purpose front-loaded and no filler. The second sentence is a straight Vietnamese restatement of the first, which is redundant for an English-reading agent but likely serves a bilingual user base.

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 simple read-only lookup this is nearly sufficient, but with no output schema the description should say something about the shape or nature of returned rulings, and it leaves the both-params-optional behavior of a zero-required-parameter search unexplained.

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%, so the description must carry parameter meaning. It does map the two inputs implicitly (maHs = HS code, moTa = product description), which is genuine added value, but it never says whether at least one is required, whether both can be combined, or how the 3-300 character constraint on moTa and the null-allowed types affect a call.

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 names a specific verb and resource: it looks up Vietnam customs classification rulings (TB-TCHQ notices), and states the two lookup modes (HS code or product description). It is distinguishable from siblings like tra_thue or tra_chu_giai, though it never explicitly contrasts itself with them, which keeps it from a 5.

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?

Usage is only implied: an agent can infer you call this when you need precedent classification rulings rather than tariff rates or explanatory notes. There is no explicit when-to-use statement, no exclusions, and no mention of the sibling tools (tim_ma_hs, phan_loai_hs, tra_chu_giai) that an agent might confuse with this one.

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