delete_recipes_by_slug_image

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

No annotations are provided, so the description must disclose behavioral traits. However, it only states 'Delete Recipe Image' without mentioning irreversibility, permissions, side effects, or what happens to associated data. For a deletion tool, this is a significant gap in transparency.

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 very concise at three words, but this brevity comes at the cost of clarity and completeness. While it is front-loaded with the action, it sacrifices necessary detail. It is not appropriately sized for a tool with two parameters and no other documentation.

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 lack of annotations, output schema, and parameter descriptions, the description is severely incomplete. It fails to provide essential context such as how to identify the image, what happens on successful deletion, and any constraints. This is insufficient for an agent to use the tool reliably.

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%, and the description adds no meaning beyond the raw schema. The two parameters (slug, accept-language) are not explained. The agent cannot infer that slug is likely the recipe slug or how accept-language affects the operation.

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 Recipe Image' clearly communicates the action (delete) and resource (recipe image). It is specific enough to distinguish from sibling tools like create_recipes_by_slug_image and update_recipes_by_slug_image. However, it lacks clarification on whether it deletes a specific image or the entire image set, and what 'slug' refers to.

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. For instance, there is no mention of prerequisites, context for deleting an image, or comparison with update_recipes_by_slug_image or delete_recipes_by_slug. The agent receives no direction on appropriate use cases.

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