delete_recipe

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

No annotations are provided, so the description carries the burden. It explicitly discloses the irreversible nature of the operation ('This cannot be undone'), which is a critical behavioral trait. It doesn't mention other side effects, but for a simple delete this is valuable and above baseline.

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 two short, front-loaded sentences. The first sentence states the action, and the second reinforces permanence. While slightly redundant, it is concise and free of fluff, earning a high score.

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 simple one-parameter delete tool with an output schema present, the description covers the essential purpose and the key risk (permanence). It doesn't address edge cases like non-existent recipes, but the output schema likely handles return behavior. Overall, it is sufficiently complete for the tool's simplicity.

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 100% coverage for recipe_id, so the baseline is 3. The description adds no additional meaning about the parameter (e.g., where to find the ID, constraints, or how it's used). The schema itself only says 'Recipe id', which is minimal but sufficient per the coverage guideline.

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 clearly states the tool 'Permanently delete a recipe', using a specific verb ('delete') and resource ('recipe'). This distinguishes it from sibling tools like search_recipes, get_recipe, create_recipe, and update_recipe.

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 implies usage when a recipe needs to be removed, but it provides no explicit guidance on when to use this tool versus alternatives (e.g., update_recipe for deactivation) or any exclusions. It's not misleading, but the context is only implied.

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