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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the risk profile is known. The description adds that channel context is resolved internally, but it never explains what 'force' overrides or what state is skipped/destroyed — the key behavioral fact for a destructive tool — and the phrase 'ChannelOAuthId resolved internally' mildly muddles the schema's required channelOAuthId parameter.

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-loaded with the action and followed by prerequisites. No waste, though the terse phrasing ('Requires HGRApi Header channel / ChannelOAuthId resolved internally') is slightly elliptical rather than crisp.

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?

An output schema exists and annotations cover the safety profile, so return values need not be described. However, for a destructive, non-idempotent mutation with many near-identical sibling tools, the description omits the consequences of forcing and any differentiation, leaving a real gap.

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% and each parameter carries its own description, so the description need only be a baseline. It mentions 'visible order Reference' and the confirmed flag but adds no semantics beyond the schema, such as whether reference is optional or how it interacts with channelOAuthId.

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+resource: forcing processing of orders identified by a visible marketplace Reference. It is understandable on its own, but it never contrasts itself with the very similar siblings hgr_process_order_lines or hgr_manually_dispatch_order_lines, so an agent cannot tell which is right from the description alone.

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 only guidance is the precondition 'Requires confirmed=true', which merely restates the schema's required flag. There is no statement of when to force versus normally process, no circumstances that justify the destructive 'force' path, and no named alternative.

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