Agent Chef

Favorite a recipe

favorite_recipe

Mark or unmark a recipe as a household favorite to keep weekly meal picks aligned with family preferences.

Instructions

Mark (or unmark) a recipe as a household favorite.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`favorite`	No
`recipe_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`tags`	No
`steps`	No
`title`	Yes
`ratings`	No
`servings`	No
`image_url`	No
`is_public`	No
`avg_rating`	No
`created_at`	No
`public_url`	No	Indexable public page, when published
`source_url`	No
`description`	No
`ingredients`	No
`is_favorite`	No
`image_generated`	No	Photo was generated by Agent Chef, so it is safe to show publicly
`source_recipe_id`	No	Set when this is the household's copy of a Community recipe

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.1Oct 3, 2026

addedOutput schema / properties / image_generated

Added value: +{
+  "description": "Photo was generated by Agent Chef, so it is safe to show publicly",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / is_public

Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / public_url

Added value: +{
+  "description": "Indexable public page, when published",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / source_recipe_id

Added value: +{
+  "description": "Set when this is the household's copy of a Community recipe",
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedv0.1.0Sep 7, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the write-but-non-destructive safety profile is covered. The description adds the useful fact that this is a reversible toggle (mark OR unmark), but says nothing about scope (household-wide), permissions, or effects on existing favorites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the toggle behavior is stated immediately. It is efficient, though the extreme brevity contributes to the missing guidance elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. However, with 0% schema description coverage and no usage guidance, the description is too thin for a two-parameter mutation tool, leaving param meaning and invocation context to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and neither parameter is documented. The 'mark (or unmark)' phrasing loosely implies the boolean favorite flag, but the description never names the favorite parameter, its default, or explains recipe_id, leaving both params effectively undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (mark/unmark) and resource (recipe as household favorite), making the toggle behavior clear. It does not explicitly differentiate itself from the sibling get_favorite_recipes or update_recipe, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no when-to-use context, no prerequisites, and no mention of alternatives like get_favorite_recipes or update_recipe. An agent must infer usage purely from the name and the toggle semantics.

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