Create Recipes Bulk Actions Delete

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

With no annotations, the description must carry the behavioral burden. It does disclose that the operation is destructive, but it does not say whether deletion is permanent, what associated data is affected, or whether any safeguards exist. For a bulk delete, this is a significant transparency gap.

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?

Three words are concise but under-specified. The description omits necessary details about the recipes parameter and deletion scope, so this is under-specification rather than effective brevity.

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 has no annotations and no output schema, and the description does not explain the required input format, deletion behavior, or result. For a bulk destructive operation, this is critically incomplete.

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 provides no parameter meaning. The required 'recipes' array could contain IDs, slugs, or something else, and 'accept-language' is entirely unexplained. The agent is left to guess.

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' clearly names the verb (delete), the resource (recipes), and the bulk scope. It is distinguishable from singular deletion tools like delete_recipes_by_slug, though it does not contrast with other bulk-action siblings.

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 guidance on when to use this tool versus delete_recipes_by_slug or other bulk_actions like tag/categorize/export. The description implies bulk deletion but never states the intended use case, prerequisites, or exclusions.

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