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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavioral context: deletion is permanent and irreversible, and deleting a trip cascades to everything inside it including photos and documents. It stops short of describing permissions or partial-failure behavior, so not a 5.

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 short sentences, front-loaded with the action and its scope, followed by cascade behavior and irreversibility. Nothing is redundant and each sentence adds distinct information.

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?

An output schema exists so return values need no explanation, and annotations carry the safety profile. For a destructive tool, the description supplies the two facts an agent most needs before calling: that deletion is permanent and that trip deletion cascades to nested content.

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% with a single 'items' array parameter whose nested type/id fields are documented and constrained by an enum. The description's list of deletable types mirrors that enum, adding no format, ID syntax, or batch-limit detail beyond the schema, so the baseline 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?

States a specific verb ('permanently delete') and enumerates the exact resource types it operates on (trips, transport, stays, activities, expenses, packing items, photos, homes), which matches the enum in the schema and clearly distinguishes it from siblings like update_trip, save_items, and import_trip.

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?

The enumerated entity types imply the scope of use, but the description never states when to choose this tool over siblings such as update_trip or save_items, nor does it cover batching or prerequisites. Usage is implied by scope rather than explicitly guided.

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