Export recipe bundle

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

Annotations already declare destructiveHint=true. The description reinforces this by stating 'Writes a file (destructive)' and adds that output is a portable JSON bundle. However, it lacks details like overwrite behavior or permissions needed. Adequate but not rich.

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 efficient sentences: purpose, usage scenarios, and destructive warning. Front-loaded with the key action. No redundant words.

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 3 parameters and no output schema, the description should explain parameters and return behavior. It fails to specify how to select recipes (via recipe_ids or include_all) and does not describe the output format beyond 'portable JSON bundle'. Incomplete for a tool with moderate complexity.

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%. The description does not explain any of the three parameters (out_file, recipe_ids, include_all). It mentions 'selected recipes' but not how selection works via parameters. This is a critical gap for 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 clearly states the tool writes selected recipes to a portable JSON bundle on disk. It distinguishes from siblings 'import_recipe_bundle' and 'publish_recipe_bundle' by mentioning them as alternatives, providing a specific verb ('write') and resource ('recipes') with context of portability.

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 explicitly states when to use the tool: to hand recipes to another machine or to CI. It mentions alternatives (import, publish) and warns that it writes a file destructively. No explicit when-not but clear context.

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