save_expense_receipt_image

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

With no annotations, the description carries the full disclosure burden. It clearly states the write effect (saving to a local file), the optional thumbnail behavior, and the return shape. However, it does not disclose potential file overwrites, directory creation, required permissions, or failure behavior, which are relevant side effects for a file-writing tool.

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 a front-loaded one-sentence summary followed by a compact Args/Returns block. Every sentence provides necessary information with no redundancy or filler, making it easy to parse quickly.

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 three-parameter download/save tool, the description covers all parameters and the return type, and an output schema exists to formalize results. The main gaps are the lack of distinction from the near-identical sibling tool and missing detail on file-overwrite behavior, keeping it just short of fully complete.

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 input schema has 0% description coverage, providing only titles and types. The description's Args section fully defines each parameter—expense_id, save_path, and thumbnail—and documents the default for thumbnail, completely compensating 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?

The description opens with a specific action — 'Download and save an expense receipt image to a local file' — identifying both the resource and the destination. However, it does not explicitly differentiate this from the sibling download_expense_receipt_image, so the agent must infer the distinction from the save_path parameter.

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 no guidance on when to use this tool over download_expense_receipt_image or the expense query siblings. It only states what the tool does, without mentioning when to prefer it or alternatives, leaving the choice entirely to the agent.

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