Import recipe bundle

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds important behavioral context: validation before writing prevents corruption, and it explicitly states 'Writes files (destructive)'. This goes beyond annotations but could mention overwrite 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?

The description is three sentences long, with the main action first. Every sentence adds value: purpose, inverse relationship, validation behavior, and destructiveness. No unnecessary 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 no output schema, the description does not explain return values. It covers input and validation but lacks detail on success/failure behavior and the overwrite parameter. Adequate but not comprehensive.

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 coverage, the description should compensate, but it only implicitly references two parameters (bundle_file, out_dir) and completely omits the 'overwrite' parameter. It does not describe parameter formats or constraints.

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 it imports recipes from a JSON bundle into a directory, and specifies it is the inverse of export_recipe_bundle. The verb and resource are specific, and it distinguishes itself from related tools by mentioning the inverse relationship.

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 mentions it is the inverse of export_recipe_bundle, providing a clear alternative. However, it does not compare to other importing tools like import_recipe_from_url or specify when not to use it.

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