delhaize_backfill_images

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

With no annotations, the description carries the full burden and meets it: it declares this is not read-only, states exactly what is written (image files into receipts_backfill/) and what is deliberately left untouched, and explains the side-effect-free rationale (no double ingestion). It even documents the file naming convention used for pairing.

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?

Front-loads the core action and condition, then layers on safety constraints and the return shape in three tight paragraphs. Slightly longer than strictly needed but every clause carries operational 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?

No output schema exists, and the description compensates by enumerating the return keys ({missing, found, saved, missed, not_in_window, next_step}). The only real omission is the unexplained `months_back` parameter, which leaves the time-window semantics undefined.

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 single parameter `months_back` has 0% schema description coverage and is never mentioned in the description, so the agent has no idea it controls the lookback window. This is the one place the description fails to compensate for the schema gap.

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 ('Save the missing PHOTOS of Delhaize receipts') and defines the exact condition ('record has no existing `image` path and no matching file in receipts_backfill/'). This is enough to separate it from siblings like delhaize_fetch_new_receipts and delhaize_fetch_promotions.

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?

Explains precisely when the tool applies (receipt exists but lacks a photo) and explicitly scopes out adjacent operations ('never edits receipts_all.json and never uses receipts_inbox'). It does not name a sibling alternative for cases that don't qualify, so it stops short of full when/when-not routing.

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