Remove an ingredient from your WeekPlan recipes using its unique id. Use this to delete unwanted or incorrect ingredients via the WeekPlan API.
Delete an ingredient by id.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Ingredient id to delete |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, and the description merely restates the destructive action without adding anything — no mention of irreversibility, auth requirements, or effect on dependent recipes. It does not contradict the annotation, but it adds no behavioral value.
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?
A single front-loaded sentence with zero waste. It is efficient, though arguably terse to the point of under-specification rather than maximal conciseness.
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 one-parameter tool with full schema coverage and a destructiveHint annotation, the description is minimally sufficient to call the tool correctly, but says nothing about the consequences of deletion.
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% and the single parameter is fully documented in the schema, so the description's 'by id' adds nothing new. Baseline 3 applies when the schema carries parameter semantics.
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 (delete) and resource (ingredient) plus the keying field (id). It is clearly distinguishable from the add/edit_ingredient siblings, though it does not explicitly contrast itself with weekplan_delete_recipe.
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?
No when-to-use, prerequisite, or alternative guidance is given. The agent gets no signal about irreversibility or how the delete relates to edit_ingredient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.