skylight_update_recipe

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Update', which implies mutation, but gives no details about side effects, required permissions, or what happens to existing data (e.g., partial vs full update). This is insufficient for a mutation tool with zero annotation coverage.

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 concise sentence that is front-loaded with the key action and resource. However, it could be slightly expanded to include parameter details without losing efficiency.

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 complexity (5 parameters, no annotations, no output schema), the description is incomplete. It does not explain the update behavior (e.g., whether it merges or replaces fields), return values, or how it interacts with sibling tools like skylight_get_recipe or skylight_list_recipes.

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 description coverage and 5 parameters (including required 'id'), the description adds no meaning beyond the schema. It does not mention which fields can be updated or how they relate to each other, failing to compensate for the lack of parameter documentation.

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 'Update a meal recipe.' clearly states the verb (update) and resource (meal recipe), distinguishing it from sibling tools like skylight_create_recipe or skylight_delete_recipe. However, it does not explicitly differentiate from similar update tools like skylight_update_event or skylight_update_frame.

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 provides no guidance on when to use this tool versus alternatives such as skylight_create_recipe or skylight_update_event. There is no mention of prerequisites, context, or when-not-to-use scenarios.

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