Favorite a recipe

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

Annotations already establish readOnly=false and destructive=false. The description adds the toggling behavior (mark/unmark) and the household scope, which is useful, but it does not disclose idempotency, how repeated unmarks behave, or any side effects.

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?

One tight sentence that front-loads the action and scope with no filler or redundant phrasing. Every word contributes meaning.

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 two-parameter toggle with an output schema and safety annotations, the core action is clear. However, the description still leaves the agent to infer parameter semantics and supplies no guidance for choosing between this tool and get_favorite_recipes.

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 0%, so the description must compensate for parameter meaning. It only implies the recipe resource and toggle behavior; it never names recipe_id or explains how the favorite boolean controls the mark/unmark outcome beyond what can be inferred from the word 'unmark'.

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 states a specific action ('Mark (or unmark)') on a specific resource ('a recipe') with a clear scope ('household favorite'). It distinguishes the tool from lookups like get_favorite_recipes and from rating/update tools.

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 given about when to use this tool versus alternatives. The sibling get_favorite_recipes clearly relates to reading favorites, but the description never directs an agent to it or explains when the mutate-favorite tool is the right choice.

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