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

Adds substantial behavior beyond the annotations: the change becomes permanently unconfirmable, only the preparer may cancel it, and calling it on an already-confirmed change reports that fact rather than undoing it. The annotations cover the safety profile (destructiveHint=false, idempotentHint=true) and the description adds authorization and state-transition semantics without contradicting them.

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?

Purpose is front-loaded, then usage triggers, then the non-undo boundary, then id lookup and permissions. Each sentence carries distinct information, though the permission clause could have been folded into the boundary sentence.

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 the description already states what happens on a confirmed change. Auth requirement, id acquisition, and irreversibility of the cancel are all present, leaving no gap for a single-param tool.

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 100%, so the schema already defines prepare_id as a UUID. The description adds the operational route for obtaining that value ('Find the prepare_id with beleeg_look_up(what: "my_changes")'), which is meaning the schema cannot carry.

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 ('Drop') and resource ('a change that was prepared but never confirmed'), and explicitly contrasts with beleeg_confirm_change by defining the window in which the change exists. An agent can distinguish this from confirm/look_up siblings without opening a 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 concrete trigger phrases ('no', 'cancel that', 'never mind'), names the alternative path for already-confirmed changes ('the reverse has to be asked for as a new change'), and explains how to obtain the required id via beleeg_look_up. Both when-to-use and when-not are covered.

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