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

Annotations only declare that this is a non-read-only, non-destructive, idempotent operation. The description adds the critical preview/confirm two-phase behavior that no structured field encodes: the first call does not persist changes and returns a confirm_token that gates the actual write. This is exactly the behavioral trait an agent must know to avoid premature mutation.

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, front-loaded with the operation and scope, followed immediately by the mandatory workflow constraint. No filler, and the most consequential detail (gated confirmation) is not buried.

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 mutation tool with no output schema, annotations covering the safety profile, and a nested 15-field object, the description is nearly complete: it explains the scope, the confirmation gate, and summarizes the field groups. It does not state what happens to unspecified fields or whether edits are reversible, minor gaps against the otherwise strong coverage.

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 67%, with bottle_id and confirm_token documented in the schema itself. The description compensates by grouping the 15 undocumented nested 'fields' members into readable categories (notes, price, store, custom name/distillery/proof, batch, barrel details, favorite), giving meaning beyond the bare property names.

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 (Edit) and resource (your bottle) and enumerates the editable field groups (notes, price, store, custom name/distillery/proof, batch, barrel details, favorite), so the agent knows exactly the scope of the operation. It does not explicitly distinguish itself from siblings like set_bottle_status, rate_bottle, or rename_collection, so sibling differentiation is left to inference.

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 clear invocation context by spelling out the two-step flow: first call previews and returns a confirm_token, and the second call repeats identical arguments plus the token only after user agreement. It does not name an alternative tool or state when-not to use it (e.g., versus set_bottle_status for status changes), so it stops short of full routing guidance.

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