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

Annotations declare destructiveHint=true, idempotentHint=false and openWorldHint=true, and the description adds real context beyond them: it queues tracking generation per order line rather than completing synchronously, returns refreshed order data or a processing result when generation cannot start, and requires confirmed=true plus an internally resolved ChannelOAuthId header. It does not contradict the destructive hint, though it does not explain in what sense the operation is destructive (e.g. downstream supplier commitment).

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 important information (endpoint, purpose, use-when, prerequisite) is front-loaded, but the text carries boilerplate — 'This is an explicit tool with a fixed endpoint', 'Search terms: sales generatetrackingid', and repeated channel-header statements — that dilutes an otherwise tight definition.

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 mutating, open-world tool the description covers purpose, prerequisite state, required confirmation, and payload shape, and an output schema exists so return values need no elaboration. What is missing is the distinction from hgr_generate_tracking_id and any note on what 'destructive' means here, which keeps it below 5.

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%, but the body is an opaque object with no properties documented; the description compensates by naming the main field OrderLineIds: int[] and the rq type LoadAddressesFromOrderLineRequest, plus the required channel header. The confirmed and channelOAuthId semantics are already in the schema, so nothing more is needed there.

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 names the concrete endpoint (POST api/Sales/GenerateTrackingId) and states the effect: generating an HGR/VelociPacker tracking number for existing, already-processed order lines. It also explicitly denies being a generic endpoint caller. It loses a point because it never distinguishes itself from the near-identical sibling hgr_generate_tracking_id, which an agent will have to disambiguate on its own.

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?

Explicit 'Use when' clause ties the tool to the user asking HGR to generate tracking for an existing order, and it adds the prerequisite that a manually purchased supplier order must first be marked as purchased (with the HGRWeb 'Generate it' flow as analogue). No exclusions or named alternative tools are given, so it stops short of a 5.

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