verify_electronic_bill_of_lading

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

With no annotations provided, the description must carry the full behavioral burden. It discloses the validation checks performed (IMO checksum, UN/LOCODE pairs, manifest weight, AIS dark fleet screening), which is useful behavioral context, but it omits whether the operation is read-only, what permissions are required, and what the outcome or failure mode looks like.

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 tightly written sentences, front-loaded with the core purpose and followed by the specific validation scope. Every phrase earns its place.

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?

Given 10 required parameters, no annotations, and no output schema, the description is adequate but incomplete. It explains the validation scope but does not state what the tool returns (e.g., pass/fail, report) or any prerequisites, which an agent would need for a high-stakes cryptographic audit.

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 baseline is 3, but the description adds meaning beyond schema labels by explaining that carrier_imo_number is checked as a 7-digit IMO checksum, port codes are validated as UN/LOCODE pairs, and gross weight is checked against the manifest. It leaves other parameters (e.g., shipper, consignee, document hash) without added semantic detail.

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 states a specific verb ('Cryptographically audits') and resource ('UNCITRAL MLETR / FIT Alliance electronic Bill of Lading'), and lists the exact validation checks. It clearly distinguishes this eBL audit tool from sibling verification tools for minerals, origins, and trade deals.

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 usage by stating that it audits an eBL and validates specific fields, but it does not explicitly say when to choose this tool over alternatives such as verify_mineral_lot_compliance or verify_a2a_trade_deal. No prerequisites or exclusions are given.

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