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

The description discloses the destructive nature ('permanently delete') and cascade behavior (days and activities), and mentions authentication ('requires bearer token'). However, with no annotations, it lacks details on irreversibility confirmation, side effects on bookings, or prerequisites beyond the token.

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?

The description is very concise with two sentences, front-loading the key action and scope. Every sentence adds value without redundancy.

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?

Given the simple parameter (one required UUID), no output schema, and zero annotations, the description covers the essential action and cascade but omits prerequisites (e.g., itinerary must exist, user ownership) and return behavior, making it adequate but not thorough.

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 0%, so the description should explain the parameter. It does not mention itinerary_id, its format (UUID), or how to obtain it. The description adds no semantic value beyond the schema, leaving the agent to infer from context.

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 clearly states the action ('delete'), the resource ('concierge itinerary'), and the scope ('all its days and activities'), which distinguishes it from siblings like delete_activity that delete a single activity.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., update_itinerary for modifications, delete_activity for single entries). The description only states what the tool does, not when to prefer it.

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