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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered; the description adds real value by disclosing that the call fans out across DB, Shopify, and Nova Post systems and returns a comparative material analysis (sent vs current code). It stops short of noting auth requirements, rate limits, or behavior when a track trace is unknown.

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 sentences, front-loaded with the core action, then the return payload. The long enumeration is dense but each item is load-bearing information about what the caller receives from a tool with no output schema.

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 does the heavy lifting by enumerating the returned fields, which is exactly what an agent needs to decide whether this call answers its question. Missing are failure/empty-result behavior and any note on the optional intentId, keeping it below full marks.

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 only two parameters, both documented, so the schema already carries semantics. The description reinforces that the lookup is keyed by track & trace but says nothing about the optional intentId correlation parameter, so it adds little beyond the schema.

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?

States a specific verb and resource ('one-call label/material investigation by track & trace') and enumerates exactly what comes back (label createdAt, order, DB line items, Shopify line items, Nova Post material comparison). That payload enumeration implicitly separates it from thinner siblings like LookupByTrackTrace or GetLabelTrackingStatus, though it never names an alternative directly.

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 phrase 'one-call ... investigation' implies this is the consolidated option rather than a single-purpose lookup, but there is no explicit when-to-use/when-not guidance and no mention of LookupByTrackTrace, OrderInvestigation, or InvoiceInvestigation, all of which plausibly overlap. Usage is inferable but not stated.

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