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

Annotations already provide readOnly, openWorld, idempotent, and non-destructive hints. The description adds meaningful behavioral context beyond those hints: it resolves canonical identifiers, pulls SEC/GLEIF/USAspending/EPA signals, checks sanctions and public-record standing, and warns that name matches are candidates to verify. It does not cover output format details, but the annotation coverage lowers the burden.

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 three sentences and front-loaded with the core purpose, followed by supporting details and a boundary statement. Every sentence contributes: what it does, what evidence it resolves, what it returns, and what it is not. There is no filler or redundancy.

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 moderately complex tool with no output schema, the description covers purpose, evidence sources, return value, and limitations. It does not explicitly state that at least one of shipper or receiver should be provided, which is a meaningful operational gap given all parameters are optional in the schema. Overall it is largely complete but not fully self-sufficient.

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; the schema already explains each parameter. The description adds useful semantic context by stating the tool works 'for a shipper, receiver, or both' and cautioning that 'name matches are candidates to verify,' which helps an agent understand how shipper/receiver inputs are interpreted despite all four parameters being optional.

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 clearly states a specific verb+resource+outcome: it creates an evidence-backed counterparty pack for shippers, receivers, or both, and returns a review checklist for credit terms and load release. It distinguishes itself from sibling tools like counterparty_risk_score, carrier_vetting_evidence_pack, and kyb_aml_evidence_case_file by naming the shipper/receiver context and the credit/load-release use case.

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 when to use the tool through 'returns a review checklist for credit terms and load release' and provides a clear exclusion: 'this is not a credit report or endorsement.' It does not explicitly name alternative tools or give a formal when-not-to-use rule, but the contextual framing is clear enough for an agent to route the task.

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