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 genuinely useful context beyond that: the confirm gate and its 'nothing runs' behavior, plus the downstream consequence that automatic sync will overwrite the items again. That consequence is exactly the kind of risk context annotations alone 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 short sentences that front-load the action and its effect, followed by the precondition and the targeting options. No filler, though the 'AD items:' label prefix is slightly wasteful.

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 5-parameter mutation with no output schema, the description covers what the tool does, when to run it, the confirmation requirement, and the targeting modes. Only minor gaps remain, such as what happens to items not matching the given item_ids.

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%, so the schema already documents ad_id, confirm, item_ids, and all_items with the same OR-relationship wording. The description restates the confirm gate and the item_ids/all_items choice rather than adding format, ordering, or precedence details beyond the schema, 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?

The description states a specific verb and resource ('release lock' on AD items) and explicitly ties it to the sibling that created the lock ('clear the lock set by lock_ad_items'), so an agent can distinguish it from lock_ad_items and from unlock_marketplace_items without opening a schema.

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?

It gives a clear triggering condition ('Use this when frozen listings should sync again') and a hard precondition ('Needs confirm:true after the user agrees'). There is no explicit when-not guidance or named alternative, but the effect-based framing makes the selection obvious.

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