recipes_units_delete_one

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

Without annotations, the description must disclose behavioral traits. It only provides the HTTP method (DELETE) implying mutation, but fails to mention reversibility, cascading effects on recipes using the unit, or any authorization requirements.

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, but this reflects under-specification rather than efficient conciseness. It fails to include any useful information, wasting the opportunity to convey purpose and usage.

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 the tool has one parameter, no output schema, and no annotations, the description is severely incomplete. It does not explain what entity is deleted, the effects of deletion, or any error conditions, making it nearly useless for an AI agent.

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 one parameter (item_id) with a uuid4 format and no description in the schema (0% coverage). The tool description adds no additional meaning or context about this parameter, such as how to find the correct item_id or what happens if an invalid id is provided.

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 One' is a tautology that merely restates the tool name. It does not specify that it deletes a unit from the recipe system, nor does it distinguish from sibling tools like recipes_units_merge_one or recipes_units_update_one.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as whether the unit must be unused before deletion, or any context for choosing delete over merge or update.

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