neuron_recipe_delete

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

With no annotations provided, the description carries the full behavioral disclosure burden. It transparently discloses that the operation removes not just the recipe but also all associated memory/learnings, which is a meaningful side effect beyond the obvious 'delete'. It could mention irreversibility or behavior on bundled recipes, but the core destructive scope is clearly stated.

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?

Two sentences, front-loaded with the action and main object, followed by a concise limitation. Every word carries information, and there is no redundancy or filler.

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 single-parameter deletion tool with no output schema, the description captures the essential behavior, target resource, side effects, and a key limitation. It does not explain error behavior for non-existent slugs or running recipes, but these are relatively minor omissions for such a simple tool.

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 coverage is 100%, so the baseline is 3. The tool description adds meaning to the slug parameter by clarifying it must refer to a user-installed recipe and not a bundled one, which is not stated in the schema's generic 'Recipe slug to delete' description.

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 ('Delete'), names the exact resource ('user-installed recipe'), and adds scope ('and all its memory/learnings'), which clearly sets it apart from sibling recipe tools like recipe_update, recipe_get, or recipe_run. It also notes the bundled-recipe limitation, further clarifying what this tool is for.

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 states when to use it: to delete a user-installed recipe, and explicitly says bundled recipes cannot be deleted, giving a clear when-not condition. It does not name alternative tools, but no alternative deletion tool exists among siblings, so the omission is minor.

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