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

With no annotations at all, the description carries the full burden and does disclose the key side effect: contained notes migrate to their next collection or the Inbox, so nothing is lost. It does not state whether the collection deletion itself is permanent/undoable, whether nested collections or settings are affected, or what authorization is required, which are meaningful gaps 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?

Front-loaded and dense: the core behavior and its most important caveat appear in the first clause, and the consent rule closes it. The parenthetical '(as Delete collection in Caddie)' is slightly awkward phrasing but conveys a useful cross-reference and does not bloat the text.

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 two-parameter destructive tool with no annotations and no output schema, the description covers the two things an agent most needs: notes are preserved and user intent is required. Missing pieces — permanence/undo, workspace defaults, and error behavior — are modest but real, keeping it from a 5.

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 50%: `workspace` is well documented in the schema, while `name` has no description anywhere. The description adds no parameter guidance of its own (e.g., whether `name` is a display name, id, or both), so it neither compensates for the gap nor adds meaning beyond the schema.

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 collection') and immediately distinguishes the act from sibling delete_note by clarifying that notes are not deleted but reassigned. An agent can tell exactly what this removes versus what survives without opening either 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?

'Only when the user asked to' gives an explicit precondition that excludes speculative or proactive deletions, which is valuable for a destructive tool. It stops short of naming alternatives (e.g., rename_collection, move_note) or saying what to do if the user only wants to empty a collection, so it is clear but not complete routing.

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