create_recipes_bulk_actions_delete

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

No annotations exist, so the description must fully disclose behavioral traits. It fails to mention that this is a destructive, irreversible action, whether it cascades to related data, authentication requirements, or rate limits. The minimal text provides zero transparency beyond the basic verb.

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 (3 words), which is not effective conciseness but rather under-specification. It omits critical details needed for a bulk destructive operation, making it insufficient for an AI agent to use safely.

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 complexity of a bulk delete action (destructive, multiple items), the absence of output schema, and 0% parameter coverage, the description is severely incomplete. It lacks information on success/error behavior, maximum batch size, idempotency, and side effects.

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%, yet the description adds no meaning to the two parameters. The 'recipes' array is not explained (IDs, slugs, or other identifiers), and 'accept-language' is entirely undocumented. The agent cannot infer how to structure inputs correctly.

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 'Bulk Delete Recipes' conveys a clear verb+resource, but the tool name starts with 'create_' which contradicts the described delete action, potentially confusing the agent. The purpose is clear enough but lacks specificity (e.g., whether recipes refers to IDs or slugs). Without distinguishing from sibling bulk delete tools like delete_recipes_bulk_actions_export_purge, the differentiation is weak.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., single recipe deletion via delete_recipes_by_slug) or prerequisites (e.g., permissions, irreversibility). The description is silent on context, leaving the agent to guess.

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