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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds genuinely useful context beyond them: the two-stage confirmation gating ('after warning about consequences') and internal channel resolution. It stops short of stating irreversibility or what happens to related listings after termination.

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 identifier, with the confirmation requirement immediately after. The final sentence about the HGRApi header is terse to the point of obscurity and could be dropped or clarified.

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 mutation with an output schema and full parameter documentation, the description covers the essentials: what is terminated, which ID identifies it, and the confirmation gates. The remaining gap is disambiguation from sibling terminate tools and the channelOAuthId ambiguity.

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 all five parameters are already documented, making 3 the baseline. The description partly undersells the schema by saying the channel is 'resolved internally' while the schema marks channelOAuthId required, which could cause an agent to omit a mandatory parameter.

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 ('Terminates one active listing') with the identifier ('visible Product ID'), so the action is unambiguous. It does not distinguish itself from the near-duplicate sibling hgr_post_searchproduct_terminatelisting2 or from hgr_remove_listing, so an agent must inspect both to choose.

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?

Usage is implied through the required confirmation flow and the 'active listing' scope (the pendingListingId parameter hints at the pending case). However, there is no explicit when-not guidance and no mention of the sibling terminate/remove tools, which is a real selection risk in a 100+ tool namespace.

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