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

Beyond the annotations, the description discloses that unknown requestIds are idempotent no-ops and that one mode operates on in-memory unsaved cards rather than persisted data — neither is inferable from the schema. It still does not state what exactly is discarded (the patch and all subsequent ones, or only the target) or any permission requirements, which matters 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?

Three short sentences, front-loaded with the core action, then the two modes, then the edge case. No filler. A little jargon ("patch group", "drop") costs some clarity but nothing is superfluous.

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?

With a six-parameter nested schema, no schema descriptions, and a destructive annotation, the description covers the essential mode split but leaves the patches payload semantics and measurementSystem undocumented. The output schema means return values need not be explained, which keeps this at an adequate rather than poor level.

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 carries the burden, and it does explain targetRequestId and how recipeId/sessionId versus baseRecipe/patches select a mode. However, it never mentions measurementSystem, never clarifies that patches should be the remaining history after the target requestId, and gives no shape hints for the large patch union.

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?

"Drop a patch group by requestId" names a specific verb (drop/remove) and the resource (a patch group identified by requestId), which an agent can map to undoing a prior edit. The wording is somewhat jargon-heavy compared with the title "Revert Recipe Edit", but the intent is recoverable and it is clearly the inverse counterpart to apply_recipe_patches.

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 explicitly splits the two calling modes: pass recipeId/sessionId for persisted edits, or baseRecipe plus remaining patch history for a pure unsaved-card Undo. That is a concrete when-to-use-which-path instruction. It does not name sibling alternatives (apply_recipe_patches, update_recipe), so it stops short of full routing guidance.

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