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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses which tax components are computed and that official GACC schedules are the basis, but omits whether the operation is a stateless read-only calculation, how origin_country influences the applicable rate (MFN vs preferential), how invalid HS codes are handled, and result precision/rounding.

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?

A single dense sentence with no filler, and the core purpose is front-loaded. It loses a point only for leaving the acronym 'MFN' undefined while expanding both CT and VAT.

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?

With no output schema, the description should clarify what comes back; it partially does by naming the three tax types, but says nothing about result shape, currency, or whether origin_country alters the rate. For a finance-critical calculation with zero annotations and no output schema, this leaves meaningful gaps.

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 100%, so the schema already documents all three parameters, including the ISO-2 format and CNY units. The description adds no parameter-level detail; notably it never mentions that origin_country can change the applicable duty rate or that it defaults to FR, which is the one behavioral nuance the schema does not convey.

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?

Names a specific verb (computes) and resource (PRC import taxes) and enumerates the three components produced: MFN customs duty, Consumption Tax, and VAT. The GACC tariff schedule reference grounds the calculation. It does not explicitly route against siblings, though the siblings (API key provisioning, customs clearance resolution, data-transfer compliance) are in clearly different domains.

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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. Nothing explains, for example, when a user should calculate taxes here versus pursuing the clearance-resolution sibling. The agent must infer usage entirely from the name.

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