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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety bar is low, and the description adds genuine domain caveats beyond them: results reflect publisher statements only, UN approval is per design type and the authority decides plant coverage. It does not describe return shape or empty/missing-data behavior, which keeps it short of a 5.

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 payload information is front-loaded in the first sentence, and the disclaimer sentence earns its place by preventing over-reading of the results. It is dense and slightly convoluted in the opening clause, but there is no filler.

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 only three fully documented parameters, a read-only annotation set, and no output schema, the key risks an agent faces are over-interpreting the result as a compliance verdict or a certification guarantee — and the description addresses both explicitly. Nothing needed to call it correctly is absent.

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% with clear per-parameter descriptions, so the baseline is 3. The description adds meaning by framing the tool around 'the information a quotation still needs', which implies the optional intended_contents and destination_market feed that gap analysis rather than filtering the product lookup.

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 enumerates the concrete outputs for a single product: published certification and cautions, exact UN status scope, existing documents, and outstanding quotation gaps. This is specific enough to separate it from get_product_details and get_product_documents, though the opening noun phrase ('For one product, what Fortitude21 publishes about...') is not a clean verb+resource statement and no sibling is named.

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?

Strong negative scoping: it explicitly says it does NOT state what any market requires and does NOT confirm Fortitude21 holds a certificate, and it redirects to 'the dangerous goods tools on this same server' for the regulations themselves. What is missing is naming those tools (decode_un_packaging_mark, un_number_packaging) or stating when to prefer get_product_details/get_product_documents instead.

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