delete_frozen_recipe

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

Fully discloses the soft-delete behavior: the API sets count to 0 and the entry persists as history. This is crucial side-effect information, especially since no annotations are provided.

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 concise sentences that pack the key information without fluff. The structure is efficient and front-loaded.

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?

The description fully explains what happens (soft-delete, count to 0, persistence) for a simple tool with one parameter. No output schema is needed, and the scope is adequately covered.

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 only parameter 'id' has no schema description, and the tool description does not explicitly mention it. However, the action implies the id identifies the frozen entry, so the meaning is inferable but not explicitly added beyond the schema.

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?

Clearly states the action (mark a frozen entry as consumed) and the effect (soft-delete, sets count to 0). It is specific to frozen entries, distinguishing it from general delete operations.

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 context (eaten or thrown out) but does not explicitly state when to use this tool over alternatives like delete_recipe or delete_planner_event. No direct guidance on choosing this tool.

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