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

Annotations already mark this as destructive and not read-only, and the description adds important behavioral details beyond them: it affects everyone on the trip, removes associated routes, is irreversible, and requires user confirmation. This is exactly the kind of context an agent needs for a destructive operation.

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?

Two short sentences, with the destructive scope and irreversibility front-loaded before the confirmation requirement. Every sentence earns its place.

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?

The description covers the critical behavioral context for a destructive delete, and an output schema exists to explain return values. The main remaining gap is the undocumented activityId parameter, but otherwise an agent has enough information to invoke the tool 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?

Only tripId has a schema description ("from list_trips"); activityId is undocumented in the schema, and the tool description does not clarify its meaning or source. With 50% schema description coverage, the description should compensate for the missing parameter guidance but does not.

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 uses a specific verb and resource: "Deletes an activity." It also states the scope ("from the trip for everyone") and cascade behavior ("with its routes"), which clearly distinguishes it from update_activity, move_activity, and remove_list_item.

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 gives clear usage context by warning that the action cannot be undone and instructing the agent to confirm with the user first. It does not explicitly name alternatives such as update_activity for non-deletion changes, but the deletion context is clear.

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