neuron_recipe_create

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

With no annotations, the description carries the full burden of disclosing side effects. It clearly states that a new recipe is saved to ~/.neuron/recipes/<slug>/ and describes the required file contents. However, it does not mention duplicate-slug behavior, overwrite semantics, validation, or what the tool returns.

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 three sentences with no filler. It front-loads the purpose, then efficiently packs required input fields, file roles, and the destination path into tight parentheticals.

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 create operation with 5 required params and no output schema, the description gives enough to invoke correctly: inputs, file structure, and save location. It is incomplete on edge behavior like what happens if the slug already exists and what the expected response/confirmation is.

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 100%, so the baseline is 3. The description adds useful file context by mapping agent_md to 'agent.md content' and recipe_yaml to 'recipe.yaml content', but the schema already documents the required sections, so the added value is limited.

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 opens with 'Create a new recipe from scratch', which is a specific verb and resource. It also defines what the recipe consists of (agent.md and recipe.yaml) and where it is stored, distinguishing it from sibling tools like recipe_update and recipe_import.

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 phrase 'from scratch' provides clear context that this is for creating a brand-new recipe rather than updating or importing an existing one. It does not explicitly name alternatives or list when-not conditions, so it stops short of a 5.

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