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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds real value beyond them: the LIVE-channel target, the MANUAL-product-mode precondition with its failure status, and the confirm:true approval gate that returns confirm_required and runs nothing. It stops short of saying whether already-live items are re-submitted or overwritten, and gives no sense of scale/rate behavior for an 'all items' operation.

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 dense clauses: what it does and its scope first, the eligibility constraint second, the invocation rule third. No filler, no restatement of the title, and the most consequential facts are front-loaded.

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 the essentials an agent needs: scope, precondition, and the confirmation handshake. Remaining gaps are the undocumented project_id and the lack of detail on what 'not_allowed' means for scope or how to recover from it.

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 67%; ad_id and confirm are well documented in the schema and the description reinforces the confirm-after-approval semantics. project_id is documented in neither place, and ad_id's 'from list_ads' origin is already in the schema, so the description adds only marginal parameter meaning.

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+resource+scope: 'AD-wide submit all — submit EVERY item to the LIVE ad channel', which clearly separates it from the item-scoped sibling submit_ad_items. The uppercase emphasis on EVERY and LIVE makes the blast radius unambiguous.

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 when: 'Use this when the user asks to publish all listings', plus a hard eligibility gate (MANUAL product mode only, else status:'not_allowed'). It does not explicitly name the narrower alternative (submit_ad_items) or say when to prefer it, which keeps this at 4 rather than 5.

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