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

Annotations already mark this as destructive and non-idempotent, but the description adds critical behavior beyond them: cascade deletion of itinerary segments, the required confirmed flag after explicit user confirmation, and removal of connected calendar events when automatic sync is enabled. This gives the agent the side-effect profile needed to warn the user before invoking.

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 sentences, front-loaded with the core action, followed by the confirmation requirement and the external side effect. Every sentence earns its place and no extraneous detail is included.

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 destructive two-parameter tool with full schema coverage and no output schema, the description covers ownership, cascade scope, confirmation gating, and external calendar sync side effects. An agent has everything needed to decide when and how to call it safely.

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%, so both parameters are already documented. The description reinforces that confirmed must be true only after explicit user confirmation, but adds no new format or syntax beyond what the schema already states, so the baseline of 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 ('Delete') and resource ('a trip owned by the authenticated user and its itinerary segments'), and the cascade scope distinguishes it from sibling tools like segment_delete or trip_restore. An agent can identify exactly what is removed without opening the 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 clearly states the prerequisite for use: confirmed=true after explicit user confirmation. It does not explicitly name an alternative (e.g., trip_restore) or a when-not-to-use condition, but the confirmation gate and ownership scope provide strong operational guidance.

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