Parse a PNG or JPEG receipt to extract itemized expenses for per-person cost splitting with exact-cent reconciliation.
Validate, privately preprocess, OCR, and parse a PNG or JPEG receipt.
| Name | Required | Description | Default |
|---|---|---|---|
| image_path | Yes | ||
| tax_included | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden; it does reveal that preprocessing is 'private' and that the tool performs a multi-stage pipeline. However, it does not disclose side effects, data persistence, error behavior, or what 'privately' concretely guarantees.
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?
A single sentence that front-loads the action and lists the processing stages without wasted words. Every element adds information about what the tool does.
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?
While an output schema exists and the tool has only two parameters, the description is too thin for an agent to call it fully correctly: tax_included semantics, usage context relative to siblings, and behavioral side effects are missing. The description gives a pipeline summary but not enough operational context.
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 description coverage is 0%, so the description must compensate, but it only supports image_path by constraining the file type to PNG/JPEG. The meaning and effect of tax_included are entirely unexplained, leaving a key parameter semantically opaque.
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 uses specific verbs ('Validate', 'OCR', 'parse') and identifies the resource ('PNG or JPEG receipt'), making the tool's function clear. It does not explicitly compare against siblings like finalize_split, but the processing focus is distinguishable from the sibling names.
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 implies usage when a PNG/JPEG receipt needs validation, OCR, and parsing, but it gives no explicit when-to-use or when-not-to-use guidance. Alternatives such as finalize_split or help_receipt are not mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.