Permanently remove a recipe from your Mealie library. Provide its slug to delete the recipe and keep your collection organized.
Delete a recipe permanently.
Args: slug: Recipe slug to delete
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. 'Permanently' usefully signals that deletion is irreversible and destructive, but it does not mention side effects on related data, permissions, or error behavior for nonexistent slugs.
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 and front-loaded: one clear action sentence followed by a minimal Args section. There is no filler or redundant content beyond the necessary parameter annotation.
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?
This is a simple one-parameter tool with an output schema available, so the description is mostly adequate. Still, it omits context about destructive consequences beyond the word 'permanently' and provides no guidance on what happens if the slug is invalid or the recipe is in use.
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 must compensate. It does add some meaning by defining slug as 'Recipe slug to delete', but it doesn't explain what a slug is, how to obtain it, or any format constraints, leaving only a minimum-viable parameter explanation.
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 verb and resource: 'Delete a recipe permanently.' This clearly distinguishes it from sibling tools like create_recipe, update_recipe, and get_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?
Usage is implied by the verb 'Delete' and the qualifier 'permanently'—an agent can infer it should call this when a recipe must be removed for good. However, there is no explicit when-to-use guidance, prerequisites, or mention of alternatives like soft-delete or update.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.