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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description usefully adds that the channel is resolved internally from the header rather than passed explicitly, but says nothing about failure modes or whether results are cached/limited.

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 compact sentences with the action front-loaded and no filler. The second sentence ('Requires HGRApi Header channel / ChannelOAuthId resolved internally') is terse to the point of being slightly ambiguous about what the caller must supply.

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 two-parameter read tool with a full output schema and complete annotations, the description covers purpose, input scoping and the auth/channel requirement. Only the relationship to the overlapping address siblings is unaddressed.

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 both parameters are already documented; the description only reinforces that 'reference' must be a visible order reference and that channelOAuthId comes from hgr_list_channels. Baseline 3 is appropriate since the schema carries the parameter 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?

Specific verb+resource (loads available shipping addresses) plus the scoping detail that the order is resolved from a visible reference. It does not distinguish itself from near-siblings like hgr_load_shipping_options or hgr_post_sales_loadaddressesfromorderline, so an agent still has to guess between them.

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?

Implies the context (an order in the sales/shipping flow) and states a prerequisite (channel / ChannelOAuthId requirement), but never says when to pick this over the address-related siblings or what happens when the reference is not found.

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