Delete a specific recipe timeline event by its unique ID. Remove unwanted entries from a recipe's timeline to keep history accurate.
Delete One [DELETE /api/recipes/timeline/events/{item_id}]
| Name | Required | Description | Default |
|---|---|---|---|
| item_id | Yes |
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided. The description only mentions the HTTP method and endpoint, without disclosing side effects (permanent deletion), permissions, error handling, or idempotency. For a delete operation, more behavioral context is expected.
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 extremely concise (one line plus HTTP path). While there is no wasted text, it sacrifices clarity. The structure is minimal, lacking a clear separation between purpose and usage.
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 simplicity of a single-parameter delete, the description omits crucial details like the permanent nature of deletion, association with a recipe, and any impact on related data. Without an output schema, more context is needed for an AI agent to act safely.
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 sole parameter 'item_id' has no description in the schema (0% coverage). The description does not explain what uniquely identifies the resource (e.g., 'the UUID of the timeline event'). The agent must infer meaning from the path, which is insufficient.
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 states 'Delete One' and includes the HTTP path, which vaguely indicates deletion of a timeline event. However, it does not explicitly name the resource type (e.g., 'recipe timeline event'), relying on the path for context. This is clear but minimal.
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 on when to use this tool versus siblings like 'recipe_timeline_create_one' or 'recipe_timeline_update_one'. The description lacks any context about selection criteria or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.