bulk_delete_recipes

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It only states 'Bulk Delete Recipes', implying destructiveness but not detailing consequences (e.g., permanent deletion, impact on related data like comments or images). Missing information about required permissions, idempotency, or error handling.

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 two lines, but includes an endpoint line that provides no additional value beyond the tool name. While brevity is good, the conciseness sacrifices clarity and informativeness. Every sentence should add value, and the endpoint is redundant.

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 tool's complexity (1 parameter with no schema description, no output schema, no annotations, and many sibling tools), the description is inadequate. It fails to specify what kind of recipe IDs are expected, the result of a successful deletion, error scenarios, or how it differs from other delete operations.

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% description coverage, meaning the parameters are undocumented. The description does not compensate by explaining that the tool expects an array of recipe IDs in the request body. Without this, the AI agent likely cannot construct a valid invocation.

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 explicitly states 'Bulk Delete Recipes', which clearly indicates the action (delete) and resource (recipes) with a scope (bulk). However, it does not distinguish from sibling tools like 'delete_many' or 'recipe_crud_delete_one', leaving some ambiguity about which tool to use for bulk deletions.

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. It does not mention prerequisites, such as requiring recipe IDs, or that it is a destructive operation. The sibling list includes multiple delete-related tools, but the description offers no context to differentiate them.

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