delete_recipe_tag

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

The description discloses that deleting a tag does not impact the recipe itself and that the tag is removed from recipes. This provides clear behavioral context. However, no annotations exist (e.g., destructive hint), so the description adds value beyond structural metadata.

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 three sentences, front-loads the purpose, and provides necessary behavioral details without any redundant information. Every sentence adds value.

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 deletion tool with one parameter and no output schema, the description fully covers the operation's effect on the tag and associated recipes. It addresses key behavioral aspects and is sufficient for agent decision-making.

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 description does not elaborate on the required parameter 'item_id' beyond its presence. The input schema has no description for the parameter, and schema description coverage is 0%. The description fails to explain what 'item_id' represents (e.g., the tag's UUID) beyond inferring from the URL path.

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 explicitly states 'Delete Recipe Tag' and explains it removes a tag from the database. It clarifies that deleting a tag does not impact recipes but removes the tag from recipes that contain it, distinguishing it from other tag-related tools like bulk_tag_recipes or organizer_tags_create_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?

The description implies the tool is for deleting tags and notes that it does not affect recipes, but it does not explicitly state when to use it versus alternatives or provide conditions for safe use. No comparison to sibling tools is given.

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