Create Recipes Bulk Actions Export

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

With no annotations, the description carries the full burden, and it only says 'Bulk Export Recipes.' It does not disclose that this is a create operation that likely produces a stored export for later download, whether the export is generated asynchronously, or what side effects occur. The tool name hints at creation, but the description itself doesn't explain the behavior.

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?

'Bulk Export Recipes' is a short, scannable phrase with no filler or redundancy. However, it is more under-specification than structured description; it lacks the sentence-level clarity that would make the tool's purpose and behavior fully legible.

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?

For a tool with three parameters, no output schema, no annotations, and a visible export lifecycle among siblings, this description is incomplete. It never tells the agent what the call returns, how to retrieve the exported file, or why the required `recipes` argument is shaped the way it is.

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 parameter detail. It does not define what kind of identifiers go in `recipes`, what `exportType` controls beyond the `json` enum, or the role of `accept-language`. Only the word 'Recipes' maps to the `recipes` parameter, leaving the other parameters unexplained.

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?

'Bulk Export Recipes' clearly names the action (export) and resource (recipes), so an agent can identify its core purpose at a glance. It does not explicitly distinguish this create-export step from siblings such as list_recipes_bulk_actions_export or list_recipes_bulk_actions_export_by_export_download, so it doesn't earn the top score.

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 gives no guidance on when to choose this tool over the closely related export siblings (list_recipes_bulk_actions_export, list_recipes_bulk_actions_export_by_export_download, delete_recipes_bulk_actions_export_purge). There are no usage conditions, prerequisites, or exclusions.

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