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

Annotations already flag destructiveHint=true and idempotentHint=true; the description adds the non-obvious side effect that changing the search discards deals found so far, which is genuinely useful beyond the annotations. A confirmation requirement is also surfaced. It does not detail permissions or the response shape.

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?

Front-loaded with the action and a compact enumeration, then two short constraint sentences. Every sentence earns its place; the field enumeration is slightly long but substitutes for scanning the schema.

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?

With an output schema present and rich annotations, the description's job is mostly update semantics and side effects, both of which it covers. Missing only explicit routing to sibling tools, which is minor given the dense schema.

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 100% across 19 parameters, with rich per-field descriptions (units, ranges, flight vs hotel applicability), so the baseline is 3. The description's field list ('price bar, months or date window, nights, stops, airlines, preferred weekdays, name, guests, stars, channels') broadly maps to but does not enrich the schema, and 'guests' loosely corresponds to the 'adults' property.

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 (bucket list) and enumerates the editable facets, so the agent knows exactly what this tool mutates. It does not explicitly differentiate from the add_*_bucket_list siblings, relying on 'edit' to imply an existing list, which keeps it just short of a 5.

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 operating context: only supplied fields change, a changed search resets prior deals, and 'Confirm first' signals a prerequisite. It does not name sibling alternatives (e.g., use add_flight_bucket_list to create), so it stops at 4.

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