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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true). The description adds behavior they cannot convey: the operation is a consent-gated two-phase call where the first invocation is non-mutating and only returns a confirm_token, and the underlying bottle is preserved. That is exactly the kind of state/authorization context an agent needs.

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 sentences, zero filler, and the outcome/scoping constraint is front-loaded before the procedural detail. Every clause earns its place.

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?

No output schema exists, and the description does cover the meaningful return value of the first call (confirm_token) plus the consent gate. It does not mention error cases or what the post-removal state looks like, but for a 3-parameter tool with full schema coverage this is nearly complete.

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 description coverage is 100%, so the schema already documents bottle_id, collection_id, and the confirm_token omit/retry semantics in detail. The description restates the confirm_token flow but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

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 ('take one of your bottles out of one of your collections') and immediately disambiguates from the destructive sibling remove_bottle by clarifying 'the bottle stays on your shelf.' An agent can distinguish it from add_to_collection, remove_bottle, and delete_collection 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 two-step usage protocol: the first call previews and returns confirm_token, and the second call is only made 'after they agree.' The condition that triggers the second call is spelled out. It stops short of naming alternative tools (e.g., remove_bottle) by name, so it is clear context rather than full when/when-not routing.

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