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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description goes further with real behavioral context the annotations cannot express: visibility effects ('Published lists show them immediately; private lists stay private') and a scoped auth requirement ('Requires lists.publish only for a published destination'). It stops short of stating what happens on a stale or already-consumed reviewId beyond the retry instruction.

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?

Four sentences, each carrying a distinct payload: purpose, side effects, scope guard, and failure path, with purpose front-loaded. Slightly dense and could drop one clause without loss, but there is no filler.

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 mutating, open-world tool with no output schema, the description covers the precondition, the permission needed, the observable side effects, and the recovery path when the preview is stale. What is missing is the result of a successful confirm (e.g., what the agent should report back), though the absence of an output schema limits how much is expected.

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?

There is a single parameter and schema coverage is 100%, with reviewId already documented in the schema as coming from review_items. The description reinforces that linkage but adds no format, lifetime, or validity detail beyond it, so the baseline 3 for fully documented schema 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 ('finish adding those exact picks') and anchors it to a named predecessor step, review_items, which separates it from sibling writers like add_item, add_items, and stage_picks. An agent can tell this is the commit step of a review-then-confirm flow without opening any 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?

Gives an explicit precondition ('After the person approves the enriched preview from review_items'), a boundary on scope ('Never approves unrelated edits'), and an alternative path when state has drifted ('If the preview changed, call review_items and show the refreshed picks'). When, when-not, and the fallback tool are all named.

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