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

Beyond the annotations, the description discloses that a linked account is required, that validation is against the brief, and that status needs_revision saves nothing while returning fixes and a fresh token. It also explains that status saved means the recipe is in the library and appUrl opens it, which is substantial behavioral context for a write operation.

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 front-loaded with the core action and then adds only decision-relevant details: source scenarios, token dependency, validation behavior, success/failure outcomes, and account requirement. Despite its density, every sentence contributes to correct invocation or interpretation.

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 complex mutation tool with an output schema, the description covers the essential context: account prerequisites, token provenance, validation rules, and the two meaningful status outcomes. The output schema can carry return-shape details, so the description is complete without needing to restate them.

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?

With 13 parameters and only 69% schema description coverage, the description adds important meaning for recipeDraftToken by tying it to start_recipe and explaining the validation brief. It also clarifies required-field expectations around UK ingredient names, metric quantities, sections, method cues, and plain title, though it does not explain several optional params such as tags, servings, or times.

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 structured recipe into the Chop It library — and explicitly names the three supported origins: cookbook photo, user-created recipe, or corrected import. It also links the call to start_recipe and its recipeDraftToken, so an agent can distinguish this from import and discovery siblings.

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?

It gives clear usage context: call after start_recipe and pass the returned recipeDraftToken. The three source scenarios imply when this tool is appropriate, though it does not explicitly name when to prefer import_recipe_from_image, import_recipe_from_url, or save_discovered_recipe instead.

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