delete_saved_meal

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds the authentication requirement, which is not in annotations. It does not elaborate on idempotency behavior (e.g., error on double deletion) or any side effects, but the annotation coverage is adequate.

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 sentences with no wasted words. The purpose is front-loaded, and every sentence adds value: purpose and prerequisite.

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 tool with no output schema, the description covers the basic purpose and prerequisite. However, it does not address return value, error conditions, or cascade effects on items. Given the presence of delete_saved_meal_item, more context about the scope of deletion would improve completeness.

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?

Schema description coverage is 100%, with the parameter described as 'Saved meal ID to delete'. The description simply repeats the same information without adding extra context about ID format or source.

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 'Delete a saved meal' with a specific verb and resource. It correctly distinguishes from sibling tools like delete_saved_meal_item by focusing on the entire saved meal rather than individual items.

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 only provides an authentication prerequisite but gives no guidance on when to use this tool versus alternatives like delete_saved_meal_item. It does not explain when it is appropriate to delete a saved meal rather than an item.

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