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

Annotations already flag destructiveHint=true and non-idempotent, and the description adds substantive context beyond them: imported listings are always activated, ToRelist is ignored, UserDevice must be omitted and never invented, internal-only fields are stripped, and the channel header is resolved internally. It also describes the response shape (inserted, invalid, repeated, quota entries) and the VAT-preservation nuance.

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 useful content is buried behind boilerplate: a restated endpoint path, a defensive 'it is not a generic endpoint caller' disclaimer, and a 'Search terms:' line that adds nothing for an agent. Front-loading suffers because the actual purpose only appears after that preamble, and the payload instruction is repeated.

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 need not explain return values, yet it still summarizes them usefully. For a destructive, open-world mutation requiring confirmation and an internally-resolved channel header, the coverage is solid; the one missing piece is disambiguation from the sibling variant.

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 baseline would be 3, but the description goes further by explaining body internals the schema leaves as an untyped object: OAuthId, Listings (ListingToMonitor[]), the ignored ToRelist field, and that UserDevice must be omitted by MCP clients. The channelOAuthId linkage to hgr_list_channels is only in the schema, not the description.

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: 'Imports or monitors existing channel listings in HGR', with the important side effect that imported listings are always activated. It does not distinguish itself from the near-identical sibling hgr_post_channellisting_monitorexistinglisting2, which an agent could easily 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?

'Use when concrete existing store listing/product ids and source URLs are already selected and the user wants HGR to monitor/import those existing listings' gives a concrete triggering condition, plus the confirmed=true prerequisite. However, it never names an alternative or exclusion — critically, it is silent on when to prefer the ...monitorexistinglisting2 sibling.

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