skylight_update_recipe

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Update' and does not explain whether fields are partially or fully replaced, whether the operation is reversible, what permissions are needed, or what the response contains. This is a significant gap for a mutation tool.

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 short and contains no filler, but it is under-specified rather than appropriately concise. A single clause that restates the tool's name does not provide meaningful structure or front-loaded decision information for an agent.

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?

For a 5-parameter mutation tool with no output schema, no annotations, and 0% schema coverage, a one-sentence description is completely inadequate. An agent cannot determine which fields are updatable, what the identifiers refer to, or what the call will return.

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% and the description mentions none of the five parameters. While names like id, summary, and meal_category_id are somewhat suggestive, nothing clarifies what frameId means or how the fields are applied during an update.

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 uses a specific verb ('Update') and names the resource ('meal recipe'), which clearly distinguishes it from sibling create/delete/list recipe tools. It doesn't explicitly contrast with those siblings, but the core operation is unambiguous.

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?

There is no guidance on when to use this tool versus skylight_create_recipe or skylight_delete_recipe, and no mention of prerequisites such as the recipe already existing or id identifying the target recipe. The schema's required id hints at existing-resource semantics, but the description does not state this.

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