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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description still adds real value beyond that: it discloses the exclusion rule (active products and every recoverable PrimaryId, including variations, are omitted from Listings), the two-collection return shape, and that the channel header is resolved internally. It does not discuss pagination or volume limits, which is the remaining gap.

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 and usage trigger are front-loaded, but there is padding: the 'explicit tool with a fixed endpoint; not a generic endpoint caller' sentence restates the obvious, the raw endpoint path duplicates the tool name, and the 'Search terms:' line is keyword stuffing. The labeled sections (Purpose/Input/Output/Use when) do make it scannable.

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 one-parameter read tool with annotations and an output schema, the definition covers trigger, scope, input source, and the semantics of both returned collections, which is more than enough to call it correctly. Only absence of any size/pagination expectations keeps it short of full marks.

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 the single parameter is already documented as the ChannelOAuthId from hgr_list_channels, so the baseline is 3. The description's statement that the channel header/ChannelOAuthId is 'resolved internally' sits slightly at odds with the required explicit parameter and adds no format or sourcing detail beyond the schema.

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 (GET api/SearchProduct/getMissingListings), the entity (missing_listing), the operation (list_missing), and the scope (current store). It is easy to distinguish from most siblings, but it never names the closest alternatives (e.g. hgr_get_pending_listings or hgr_post_searchproduct_getpendinglistingsimages2) that an agent might confuse it with.

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 explicit 'Use when: the user asks which products from the current store can be imported or recovered into HGR' gives a clear trigger condition. There are no when-not conditions and no pointers to sibling recovery tools, so the guidance is clear but not exhaustive.

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