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

Annotations already declare it is a non-idempotent, open-world, non-read-only write, so the bar is lower; the description still adds real value by disclosing the account link requirement, a per-conversation rate limit, and a paid-processing confirmation gate. The rate limit is stated only as 'Limited per conversation' without numbers, which keeps it from a 5.

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 core purpose and source types are front-loaded in the first sentence, and each subsequent sentence adds a distinct operational fact (review path, paid confirmation, limits, auth). It is dense but nearly every clause earns its place; a small trim of the redundant 'requires a linked Chop It account' phrasing would tighten it further.

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 multi-step, account-gated, potentially paid import tool, the description covers the main decision points: review outcome, follow-up save, payment confirmation, and rate limits, and an output schema exists so return shapes need not be explained. It could still be clearer about failure behavior when neither url nor caption works, and about how it differs from the image-import sibling.

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 coverage is 100%, so the schema already documents url, caption, requestId lifecycle, and the confirmPaidImport credit condition in detail. The description's parameter-related statements (caption as fallback, requestId/confirmPaidImport flow) largely restate the schema, so the baseline 3 applies despite minor flow-level reinforcement.

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?

States a specific verb and resource with source scope: 'Imports a recipe from a link (TikTok, Instagram or any recipe website), or from pasted caption text,' and names the outcome (restructured to Chop It's standard, saved to library). It does not explicitly distinguish itself from the close sibling import_recipe_from_image, leaving the link-vs-image boundary implicit.

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?

Gives concrete usage context: use caption when the link can't be read, follow a needs_review result with save_recipe, and call confirmPaidImport only after the user agrees. It also states prerequisites (linked account, per-conversation limit). Missing an explicit 'use this instead of X' contrast against import_recipe_from_image or save_discovered_recipe.

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