Export recipe bundle

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

The annotations indicate destructiveHint=true, but the description does not elaborate on what destructive actions occur (e.g., overwriting files). It simply says 'write', lacking context about permissions, side effects, or reversibility.

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 a single sentence that is concise and front-loaded. While efficient, it could be slightly more informative without sacrificing 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?

Given the destructive behavior, lack of output schema, and three parameters, the description is too minimal. It does not specify return value, error conditions, or relationship to similar tools like import or publish.

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 coverage is 0%, and the description does not explain parameters like out_file, recipe_ids, or include_all. The meaning of 'selected recipes' is ambiguous without clarifying how selection works (ids vs include_all).

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 verb 'Write' and the resource 'selected recipes' to a specific output format 'portable JSON bundle'. It distinguishes the tool from siblings like import_recipe_bundle and publish_recipe_bundle.

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 implies usage for exporting recipes as a portable bundle but does not provide explicit guidance on when to use it versus alternatives (e.g., publish_recipe_bundle) or exclude cases.

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