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

Beyond the annotations (destructiveHint: true), the description explains the soft-delete nature and the automatic conversion of linked meal plan entries into custom snapshots. This is valuable behavioral context that helps the agent understand consequences and is not contained in the annotations or schema.

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?

The description is two sentences long, opens with the primary purpose, and includes the most important behavioral caveat (soft delete and meal plan snapshot). No unnecessary words or repetition.

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 tool has a single, well-documented parameter, and the description covers the key side effect (meal plan conversation). The output schema exists, so return values need no explanation. The description is complete for the tool's complexity and context.

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?

The schema already documents the 'id' parameter fully (including its source from list_recipes), so the description adds no additional semantic value. With 100% schema coverage, the baseline of 3 is appropriate.

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 states a specific action ('Delete a recipe') and identifies the resource ('the household's collection'), clearly distinguishing it from sibling delete tools for other entities. The soft-delete detail further adds specificity and clarifies the tool's behavior.

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?

The description implies when to use this tool (to remove a recipe from the household's collection) and provides important context about the effect on meal plan entries. However, it does not explicitly mention alternatives or when not to use it, though the purpose is clear enough for a delete operation.

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