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 safety profile is covered structurally. The description adds genuinely useful context (requires confirmed=true and impactConfirmed=true, references the ChannelOAuthId header), but also claims the channel is 'resolved internally' while the schema requires channelOAuthId as a caller-supplied required parameter, muddying rather than clarifying behavior.

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 tool identity is front-loaded, but the text is padded with boilerplate ('Dedicated HGRApi tool for...', 'This is an explicit tool with a fixed endpoint', 'Search terms:') and a tautological usage sentence. Several sentences restate the tool name rather than adding information.

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, so return values need no explanation, and the confirmation semantics are covered. Still, the body payload structure is only hinted at via OrderLineIds, and the internal-vs-caller-supplied channel token ambiguity is left unresolved for a high-impact destructive operation.

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%, so the baseline is 3; the description does add that the body's main field is OrderLineIds: int[], which the untyped body schema does not convey. That value is partly offset by the 'ChannelOAuthId resolved internally' claim that conflicts with the required channelOAuthId input.

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 a specific verb+resource (POST force process order line in sales/order operations) and states it is a fixed-endpoint tool, not a generic caller. However, it gives no differentiation from very close siblings like hgr_force_process_order_lines, hgr_post_sales_processorderline, or hgr_post_sales_fixedorderline, so an agent cannot confidently choose among 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?

The 'Use when' clause merely restates the tool name ('use it when a client needs to run the force process order line operation'), offering no situational context, prerequisites, or exclusions. The confirmation-gating requirement is the only actionable guidance and it is a schema requirement, not alternative-selection guidance.

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