skylight_delete_recipe

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

The description states 'Delete', implying a destructive action, but lacks details on reversibility, side effects (e.g., removal from meal plans), whether the recipe must exist, or any required permissions. No annotations are present to compensate.

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, front-loaded sentence with no wasted words. It conveys the core action efficiently.

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 destructive nature of the tool, lack of output schema, and two underdocumented parameters, the description is far too sparse. It does not explain what the ID represents, the effect of the optional frameId, nor what happens after deletion.

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?

The schema has two parameters ('id', 'frameId') with 0% description coverage. The description does not explain their meanings, roles, or relationships, leaving the agent unsure which ID to provide.

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 'Delete a meal recipe.' uses a specific verb ('Delete') and clearly identifies the resource ('meal recipe'), distinguishing it from sibling tools like create, update, or list recipes.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., skylight_update_recipe for deactivation), nor are there prerequisites or conditions for deletion.

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