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

Annotations already declare destructiveHint/idempotentHint, but the description goes well beyond them: it specifies the cascade (non-completed trips without participants are deleted), what is preserved (completed trips kept as history, keptCompletedTrips), the side effect on the website draft, and the exact blocking error code itinerary.delete_blocked_by_trips with its details.trips payload. This is rich, non-redundant behavioral disclosure.

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, then the cascade and failure semantics; nearly every clause carries real information. It is dense and would scan better as short clauses or bullets, but there is no filler.

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 tool with a single required param and an output schema, the description covers the cascade scope, the partial-deletion outcome, the blocking failure mode, and the preserved history. Nothing an agent needs in order to call it safely is missing.

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 must compensate, and it only says "id (uuid)" – information already conveyed by the schema's format/pattern. It does not say which program the id refers to or where to obtain it, so it adds little beyond the structured field.

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 and resource ("Delete a travel program") that cleanly distinguishes it from the delete_trip, delete_template, and delete_*_item siblings. An agent can identify the target entity 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?

Gives a clear precondition for invocation and a remedy: deletion stops if an open trip with participants exists, and the agent is told to cancel or complete them first. It also notes publishing is a separate step, but it never compares against a non-destructive alternative (e.g. update_program) for cases where removal is not intended.

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