bulk_export_recipes

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

No annotations are provided, so the description carries full burden. It does not disclose key behaviors such as whether export creates a file, the supported output format, or if the operation is synchronous. The lack of details makes the tool's behavior opaque.

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 brief but under-specified. It only repeats the title and adds an HTTP endpoint, which is not useful for an AI agent. Every sentence should earn its place; here the endpoint could be removed without loss.

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 the sibling tools and the absence of annotations, the description is woefully incomplete. It does not specify the output format, return behavior, or how it differs from tools like bulk_categorize_recipes. An agent cannot reliably invoke this tool based on this description.

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?

With 0% schema description coverage, the description must explain parameters but fails to do so. It does not mention that 'recipes' is a required array of IDs or that 'exportType' defaults to 'json'. No value is added beyond the schema's raw structure.

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 Export Recipes' restates the tool name without a clear verb like 'exports' or 'downloads'. It fails to specify that this tool exports multiple recipes in a given format, and does not differentiate from sibling bulk tools like bulk_delete_recipes.

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 individual export or other bulk operations. The description omits any context about prerequisites, alternatives, or appropriate use cases.

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