delete_users_by_id_favorites_by_slugRemove a recipe from a user's favorites by providing its UUID and slug. Use this to clean up saved recipes or update favorite lists directly.
Removes a recipe from the user's favorites
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| slug | Yes | ||
| accept-language | No |
Changes observed during successful MCP inspections.
v3.20.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the mutating action ('Removes') but does not disclose permissions, idempotency, permanence of the removal, or behavior when the favorite does not exist.
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 filler. Every word contributes to conveying the tool's core purpose.
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 tool with no annotations and no output schema, the description is too sparse to fully support correct invocation. It omits parameter meaning, usage context, and behavioral caveats, leaving an agent to infer critical details from the tool name.
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 does not explain that 'id' is the user UUID or that 'slug' is the recipe slug. It only provides domain context ('user's favorites') rather than explicit parameter semantics.
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 the specific verb 'Removes' and clearly states the resource ('a recipe from the user's favorites'). This distinguishes it from sibling tools like create_users_by_id_favorites_by_slug (adds a favorite) and list_users_by_id_favorites (lists favorites).
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 explicit guidance about when to use this tool versus alternatives, no prerequisites, and no mention of related create/list operations. Usage is only implied by the verb 'Removes'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.