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

Beyond the annotations (readOnly, idempotent, openWorld), the description adds real behavior: the header channel is resolved internally from ChannelOAuthId, Site defaults to the current store country, and the tool keeps a configured product-link selector, using all page links only when none is configured. These are non-obvious operational details that the annotations do not convey.

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 purpose is front-loaded, but the text carries boilerplate: the endpoint is restated, there is a redundant 'Search terms' line, and both 'Send the exact request payload in body' and the header-channel note are repeated in spirit. It is usable but several sentences do not pull extra weight.

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 an output schema present, the description does not need to explain return formats, and it still summarizes that supplier-specific extraction settings come back. Required params and the channel resolution are covered, leaving little ambiguity for a two-parameter read-only call.

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, but the description goes further by explaining what Url and Site mean in context and that the channel comes from ChannelOAuthId resolved internally. It also states that the exact request payload must be sent in the body, which guides correct invocation.

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 and resource: it returns supplier page extraction settings for the listing extension and bulk publication, via a fixed endpoint. It explicitly distinguishes itself from a generic endpoint caller, so the agent knows this is not a passthrough proxy. However, it never contrasts itself with the many similar hgr_post_listing_* siblings, so the differentiation stops short of naming an alternative.

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?

A concrete 'Use when' clause is given: identify product details and product links from a supported supplier page. It also states the tool is fixed-endpoint rather than a generic caller, which implicitly rules out misuse. The description gives no explicit when-not guidance or named alternative for other listing-setting scenarios.

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