delete_recipe_image

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

No annotations are provided, so the description carries the full behavioral burden. It never states that this is destructive/irreversible, whether it requires ownership or permissions, what happens if no image exists, or what is returned. The only behavioral signal is the DELETE verb embedded in the path, which is already implied by the tool name.

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 operative content ("Delete Recipe Image … Delete image … [DELETE /api/recipes/{slug}/image]") is front-loaded and clear, but the long keyword dump ("destroy image, write image, delete, remove, destroy, write, mealie…") is filler that adds no semantic value and bloats the definition.

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 destructive, single-parameter mutation with no annotations and no output schema, the description should at minimum disclose irreversibility, required permissions, and the target of deletion. None of that is present, leaving an agent unable to judge consequences of the call.

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 0% (the single `slug` parameter has no description), but the description partially compensates by embedding {slug} in the endpoint path, showing it identifies the recipe. It adds no format, uniqueness, or lookup semantics beyond that placement.

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+resource ("Delete Recipe Image", "Delete image") and even gives the endpoint DELETE /api/recipes/{slug}/image, so an agent knows exactly what operation this performs. It does not, however, contrast itself with adjacent siblings like update_recipe_image, upload_recipe_asset, or get_recipe_img, so the differentiation is left to inference.

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?

There is no when-to-use or when-not-to-use guidance, no mention of alternatives, and no prerequisites. The HTTP verb and path imply it removes an existing image, but nothing tells the agent under what circumstances to reach for this versus replacing the image.

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