Prepare receipt image analysis

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, non-idempotent), so the bar is lower. The description usefully adds that the upload is 'staged' and that 'Analysis records are stored by ReceiptCal,' plus the 'allowed directory' constraint. It does not explain what staging entails (e.g., a follow-up confirm_action) or any validation/failure behavior.

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?

Two short sentences, zero filler, with the core action front-loaded before the storage note. Could be tightened slightly but is efficient.

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 single-parameter staging tool with no output schema and annotations already covering safety, this is nearly adequate: formats, directory restriction and record storage are covered. The notable gap is any hint about the staging/confirmation workflow that the 'prepare_*' naming implies.

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 0% schema description coverage, the description must carry the burden: it names accepted image formats and the 'allowed directory' constraint, which is real meaning beyond the bare 'string' schema. However it never explains what an allowed directory is, path syntax, or what happens if the path is rejected, so it only partially compensates.

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+resource: 'Stage an upload of a local ... receipt image.' The format list (PNG, JPEG, HEIC, WebP) confirms it is the image variant, implicitly distinguishing it from the sibling prepare_analyze_receipt_text, though that sibling is never named.

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?

Usage is only implied: the agent infers it should use this tool when it has an image file and the text variant when it has text. There is no explicit when-to-use/when-not statement and no reference to the prepare_analyze_receipt_text alternative in the sibling set.

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