Delete Recipes By Slug

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

The description explicitly discloses the destructive nature of the operation by saying 'deletes', which is important given there are no annotations. However, it does not disclose whether deletion is permanent, cascades to related data, or requires specific permissions, leaving some behavioral context unstated.

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 a single, front-loaded sentence with no filler or repetition. It is concise and structurally clear, though it is sparse enough that it sacrifices some useful context.

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 is relatively simple with one required parameter and no output schema, so the description covers the essential invocation. Still, the lack of any annotation and the omission of side effects and optional parameter semantics leaves the description only minimally complete for an agent.

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 description adds meaning to the 'slug' parameter by clarifying it is the recipe identifier, which goes beyond the bare schema property. However, the optional 'accept-language' parameter is not mentioned at all, and schema description coverage is 0%, so the description only partially compensates for the missing parameter documentation.

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 clearly states the action (deletes), the resource (recipe), and the identifier (slug), so an agent knows what the tool does. It does not explicitly differentiate itself from sibling delete operations like delete_recipes_by_slug_image or delete_recipes_bulk_actions_delete, but the core purpose is unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as bulk delete, nor does it mention prerequisites or consequences. It only implies the obvious use case of deleting a single recipe by slug, without stating exclusions or preferred selection criteria.

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