Delete a specific household recipe action using its item ID to remove unwanted entries and keep your recipe data organized.
Delete One [DELETE /api/households/recipe-actions/{item_id}]
| Name | Required | Description | Default |
|---|---|---|---|
| item_id | Yes |
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits. It fails to state that this is a destructive operation that permanently removes a resource, nor mentions any authorization requirements or side effects.
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 extremely concise (two lines), but it lacks substance. While there is no wasted text, the brevity comes at the cost of informativeness.
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?
Given the simple CRUD nature, the description is incomplete. It does not cover return values, error conditions, or the effect of deletion. No annotations or output schema compensate.
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 input schema has 0% coverage, and the description provides no explanation of the 'item_id' parameter beyond its name and type. The agent cannot infer what the parameter represents or how to obtain it.
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 'Delete One' combined with the endpoint path clearly indicates the tool deletes a single household recipe action, distinguishing it from sibling CRUD tools like create, get, update.
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 guidance on when to use this tool versus alternatives. It does not mention that it should be used to delete a specific recipe action, nor does it provide context for prerequisites or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.