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

Goes well beyond the annotations by disclosing the async pipeline model, the enrichment/market-data steps, the return shape (pipeline ID plus non-blocking `suggestions` with concrete examples), and the exact failure mode (unmet readiness checklist, including photos not cleared by moderation). This is the behavioral detail the destructiveHint and openWorldHint flags don't 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?

Three tight sentences, front-loaded with the action, then returns, then failure conditions. No filler and each sentence carries distinct 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?

With no output schema, the description carries the return-value burden and does so fully — pipeline ID for tracking plus the `suggestions` payload and its purpose. Combined with the documented failure conditions, an agent has everything needed to call it and relay results.

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?

The single parameter (hashid) is fully documented in the schema, so the description adds no meaning beyond it. The description's real value here is about outputs (pipeline ID, suggestions) rather than parameter semantics, so baseline 3 applies.

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 ("kick off the publish pipeline") plus the required precondition ("for a draft listing"), which cleanly separates it from get_publish_status, update_listing, and withdraw_listing. The description also names what happens downstream, so an agent knows this is an action, not a query.

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?

Gives clear preconditions — the listing must be a draft and must pass the readiness checklist, and it discloses the failure path. It implies polling via get_publish_status by returning a pipeline ID, but never names that sibling or states explicitly "use get_publish_status to track".

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