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

Annotations already flag destructiveHint=true and idempotentHint=false, so the bar is lower, but the description still adds real behavior: two-stage confirmation gating, a required consequence warning, and internal channel/header resolution. It does not state whether removal is reversible or what happens to dependent order rules, which keeps it from a 5.

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 sentences, front-loaded with the action and scoping key, with prerequisites following. Density is high but nearly every clause carries operational meaning; the header/channel phrasing is the one portion that could be tightened.

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 destructive, non-idempotent mutation with an output schema, the description covers the prerequisites, the confirmation protocol, and the ref provenance an agent needs to invoke it correctly. Missing only the post-removal state (reversibility, side effects on dependent items).

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 already defines each field, so baseline is 3; the description still adds value by linking autoOrderingAccountRef to the specific producing tool and by framing confirmed/impactConfirmed as a warning-then-confirm sequence. The note that ChannelOAuthId is 'resolved internally' sits slightly at odds with the required channelOAuthId parameter, adding mild ambiguity rather than clarity.

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 ('Removes an auto-ordering configuration') plus the exact scoping key (autoOrderingAccountRef) and scope limit ('for one visible store/channel'). This clearly separates it from the sibling hgr_save_autoordering_configuration and from the read-only hgr_get_autoordering_configuration.

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?

Gives concrete preconditions: obtain the ref from hgr_get_autoordering_configuration and pass confirmed=true plus impactConfirmed=true only after warning the user about consequences. It stops short of naming when a user should disable rather than remove a configuration, so it falls just under full alternative-routing guidance.

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