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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds real value by spelling out the two-step confirm gate and emphasizing the operation hits the LIVE marketplace. It does not say what 'force' does to any existing listing (replace vs. duplicate), which is the key behavioral risk here.

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?

Front-loaded with the resource and verb, followed by the when-to-use cue and the confirm requirement; four short clauses with no filler. The em-dash fragment style is slightly clipped but costs no comprehension.

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 destructive, open-world mutation with no output schema, the description covers targeting and the confirm gate but leaves the consequence of a force insert ambiguous. An agent still cannot tell whether existing live listings get replaced, duplicated, or re-pushed, which matters before firing a destructive call.

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 80% and the schema already documents confirm, item_ids, all_items and marketplace_id, including the item_ids/all_items exclusivity. The description restates that choice without adding format, limits, or meaning for project_id, which is undocumented in both places. Baseline 3 is appropriate.

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 scope ('force a fresh insert of the chosen items on the LIVE marketplace') and clarifies the selection mode (item_ids or all_items). It is clearly a marketplace-side force-insert mutation, though it never explicitly names how it differs from submit_marketplace_items or pre_pair_marketplace_items, which sit right next to it.

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 a concrete triggering condition ('use this when the user asks to insert specific listings anew') and a prerequisite workflow ('needs confirm:true after the user agrees'). It stops short of naming an alternative tool or stating when NOT to use this versus a normal submit, so the agent must infer that boundary.

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