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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is carried structurally. The description adds genuinely non-redundant behavior: the manual-product-mode gate returning status:'not_allowed' and the confirm gate returning confirm_required when approval is missing. It stops short of saying whether already-submitted items are re-submitted or what the response looks like.

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?

Two tight sentences, front-loaded with scope and immediately followed by the blocking preconditions. Dense with caps for emphasis, though the parenthetical status codes make it slightly clipped rather than flowing prose.

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 bulk submit with no output schema, the description covers the essentials: what it touches, the mode restriction, and the confirmation requirement. Missing only edge details such as re-submit behavior and outcome reporting, which the annotations partially offset.

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?

At 67% schema coverage, the schema documents marketplace_id and the confirm gate, and the description mostly restates the confirm rule ('Needs confirm:true after the user agrees') with a little extra intent. project_id — the one undocumented parameter — gets no meaning from either source, leaving it unexplained.

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 with explicit scope: 'submit EVERY item to the LIVE marketplace', and the 'all' scope distinguishes it from the sibling submit_marketplace_items. The caps on MARKETPLACE/LIVE/EVERY make the blast radius unmistakable at a glance.

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 an explicit selection condition ('Use this when the user asks to publish all listings') plus hard preconditions: MANUAL product mode only, and confirm:true only after the user agrees. It does not name the subset alternative (submit_marketplace_items) for the case where only some items should be published, which is the one routing gap.

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