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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered structurally. The description adds that user confirmation is mandatory and that the channel context is inherited from the header rather than passed as a parameter. It does not say what existing tracking/reference value is overwritten or whether the change is reversible – notable gaps for a destructive setter.

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?

Three short sentences front-load what the tool does, then stack the prerequisites. No filler, though the WAPI endpoint name is jargon that adds little for an agent that cannot call the WAPI directly.

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 annotations and an output schema present, the description covers scope, the confirmation gate, and channel resolution. It still leaves behavioral effects of a destructive mutation unexplained – what value gets replaced and what happens on invalid references – which an agent needs before invoking a non-idempotent, destructive setter.

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 schema already explains confirmed, reference, and channelOAuthId. The description only reinforces the confirmed gate and clarifies that channelOAuthId is resolved from the HGRApi Header channel internally, which is mildly useful but does not exceed the schema's own detail. Baseline 3 applies.

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 – sets the manual tracking/reference state on exactly one order line – and names the underlying WAPI endpoint (ManualTrackingIdSet). The 'one exact order line' scoping plus 'manual' distinguishes it reasonably well from the tracking-generation siblings such as hgr_generate_tracking_id and hgr_post_sales_generatetrackingid, though it does not name them explicitly.

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?

'Requires confirmed=true' is a useful pre-invocation gate, and the note about ChannelOAuthId being resolved internally tells the agent the channel comes from the HGRApi header. However, there is no explicit guidance on when to choose this over hgr_generate_tracking_id or the order-line state tools (mark_as_purchased, stop_order_lines); the agent must infer it from the word 'manual'.

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