Fix/recipe tool at mention docs

[DavidKoleczek]

fix: document @mention path format requirement in recipes tool

Problem

When users ask AI to execute a recipe from a bundle, the AI would use paths like:

cli-tool-builder:recipes/my-recipe.yaml

Instead of the correct format:

@cli-tool-builder:recipes/my-recipe.yaml

This caused "Recipe file not found" errors because the _resolve_path() function only recognizes bundle paths when they start with @.

Root Cause

The tool description showed examples without the @ prefix, so AI models mimicked that pattern:

# Before (misleading)
Example:
  Execute recipe: {"operation": "execute", "recipe_path": "examples/code-review.yaml", ...}

Solution

Updated the tool description to clearly document both path formats and emphasize that bundle paths MUST start with @:

Path formats:
- Bundle path (recommended): @bundle-name:path/to/recipe.yaml (e.g., @recipes:examples/my-recipe.yaml)
- Local path: ./path/to/recipe.yaml or /absolute/path/recipe.yaml (e.g., ./my-recipe.yaml)

IMPORTANT: Bundle paths MUST start with @ to be resolved correctly.

Classification

Documentation/prompt gap - not a code bug. The underlying _resolve_path() implementation correctly requires the @ prefix; the issue was that the tool description didn't communicate this requirement to AI models.

Testing

Verified the fix by reviewing the updated tool description. The examples now consistently show:

• @recipes:examples/my-recipe.yaml for bundle paths
• ./my-recipe.yaml for local paths