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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds useful behavioral caveats: pending listing ids may be hidden unless HGRWeb shows them, and the required HGRApi channel header is resolved internally. These are helpful but relatively thin additions against the rich annotation set.

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 in the first sentence, and the following sentences add workflow and caveats without much waste. It is slightly dense but appropriately sized for an 8-parameter list tool.

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?

The tool has an output schema, full parameter coverage, and rich annotations. The description supplies the remaining operational context: store resolution, projection guidance, ID visibility caveat, and auth header behavior. It is largely complete, though it could say more about pagination behavior or the showWeListForYou flag.

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 parameter semantics are already fully documented in the schema. The description reinforces the use of fields/sortBy/sortDirection/limit for projections and answers, but it does not add syntax or meaning beyond what the schema provides.

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 states a specific verb and resource ('Lists pending listings') and scopes it to 'one visible store,' which distinguishes it from active/terminated listing tools. It does not, however, distinguish it from the sibling tool hgr_list_pending_now, which appears to cover a similar surface.

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?

It gives an explicit prerequisite workflow ('First resolve the store with hgr_list_channels') and says to do ranking/filtering/summarizing through this tool rather than post-processing. It does not state when to prefer this over hgr_list_pending_now or the pending-statistics tools, so the sibling routing is incomplete.

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