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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds substantive behavior beyond that: markup rounding rules, what happens to malformed/out-of-range markup (ignored, never deleting overrides), eBay-only VAT initialization, VAT integer 0-100 constraint, and automatic stripping of internal-only fields. It also discloses that internal channel/ChannelOAuthId resolution happens server-side.

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?

Purpose is front-loaded and the 'Use when'/'Input'/'Output' structure is easy to scan, but there is filler: a redundant restatement of the endpoint path, a 'Search terms:' line, and a repeated disclaimer about being non-generic. Several sentences could be merged without losing information.

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?

Output schema exists, so return values need not be documented, and the description covers the confirmation gates, channel resolution, and VAT/markup edge cases an agent would otherwise get wrong. What is missing is any mention of failure or partial-success behavior for a destructive, non-idempotent submit.

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 already 100%, so the baseline is 3, but the description adds real semantics the schema lacks: UserDevice must be omitted by AI chat/MCP and must not be invented, VAT must be an integer 0-100, and the body must be the exact payload. It stops short of describing the SubmitCreateRequest field set beyond 'compatible with CreateRequest'.

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 ('Submits a manually prepared listing for creation') and names the owning agent (publication). It does not explicitly contrast with the closest siblings (hgr_post_listingcreate_editpending, hgr_post_listing_savebulkpublish), so an agent must infer the boundary, but the fixed-endpoint framing prevents it being read as a generic caller.

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: ... only after manual listing creation data has already been prepared and the user wants to create or queue that exact listing' gives a clear precondition and an exclusion (not for un-prepared data). The confirmed/impactConfirmed prerequisites are spelled out. Alternatives such as editpending or savebulkpublish are never named, which keeps it short of a 5.

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