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

Annotations already establish that this is a non-destructive, idempotent write. The description adds operational context beyond the annotations: the recipe is saved unchanged, an existing copy is reused, a linked account is required, and it returns the library copy's recipeId and appUrl.

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?

Three compact sentences, front-loaded with the action and scope, followed by input source and return value. Every sentence contributes useful information without repetition.

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 simple single-parameter schema, the presence of an output schema, and the annotations covering safety and idempotency, the description provides enough context for an agent to call this correctly. It covers account prerequisites, input source, reuse behavior, and return shape.

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 schema has only one parameter and 0% description coverage. The description compensates by explaining that recipeId comes from search_recipes, get_recipe, or a menu draft, which adds meaningful source semantics beyond the bare schema field.

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 verb and resource: saving a Chop It catalogue recipe unchanged into the user's own library. It also distinguishes this from a generic save by noting that an existing saved copy is reused, and it identifies the input source as search_recipes, get_recipe, or a menu draft.

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 clear usage context: the recipeId must come from search_recipes, get_recipe, or a menu draft, and the user must have a linked Chop It account. It does not explicitly compare against sibling tools such as save_recipe or import_recipe_from_url, so it stops short of full when/when-not guidance.

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