recipe_delete

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

No annotations are provided, so the description must fully disclose behavior. It mentions removing 'manifests under ~/.local/shar...' but does not explain if the operation is reversible, requires confirmation, or what happens to dependencies. The cut-off text leaves ambiguity about the exact storage location and side effects.

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 short and appears cut off, sacrificing completeness for brevity. It lacks structure and fails to cover essential details beyond the basic 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?

Given no output schema, annotations, and zero parameters, the description should fully explain the tool's functionality. It partially does but leaves critical gaps (e.g., how to specify the recipe, what the outcome looks like).

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 input schema has zero parameters, but the description does not clarify how the tool identifies which recipe to delete (e.g., relies on context or previous selection). Without this explanation, the agent may not understand how to invoke the tool correctly.

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 explicitly states the verb 'remove' and the resource 'saved recipes/skills', distinguishing it from sibling tools like recipe_install (add) or recipe_list (list). The phrase 'one of THEIR saved recipes' clarifies scope.

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 specifies when to use ('when the user wants to remove one of THEIR saved recipes/skills'). It does not explicitly state when not to use or list alternatives, but the context is clear and no sibling tool offers similar deletion functionality.

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