delete_recipe

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only states the action and parameter, but does not mention that deletion is irreversible, whether it cascades to related data, requires authentication, or how errors are handled (e.g., non-existent id). This is a significant gap for a mutation tool.

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, direct sentence 'Delete a recipe by id.' It is front-loaded and contains no unnecessary words. Every word earns its place.

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 delete operation, the description is incomplete. It does not state what happens on success or failure, whether there are side effects, or any return value. Since there is no output schema, the description must cover these aspects, but it does not. The agent is left without critical information for invoking the tool correctly.

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 schema defines id as an integer with no description (0% coverage). The description says 'by id', which clarifies that the id refers to a recipe identifier, adding meaning beyond the raw schema. However, it does not elaborate on format or constraints, so it only partially compensates for the missing schema descriptions.

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 'Delete a recipe by id' clearly states a specific verb (delete) and resource (recipe) with an identifier, distinguishing it from sibling tools like list_recipes, get_recipe, create_recipe, and update_recipe. It is unambiguous about the action and target.

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 gives no guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or exclusions, such as whether it is for permanent deletion or if there are related tools like delete_frozen_recipe that should be used in specific cases. The agent must infer usage from the name and context.

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