AI-Invoice Parser

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

With no annotations, the description carries full burden and discloses async behavior (202 + Location poll until JSON), the side effect of saving JSON to process_invoice.json, and the returned key fields. It also notes that empty custom_field_keys are omitted. It does not cover failure modes or rate limits, but core behavior is well explained.

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 dense but efficient: each sentence adds essential information—purpose, async flow, parameter usage, and output behavior. There is no filler or repetition.

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 4-param tool with no annotations or output schema, the description covers input handling, async polling, file output, and return fields. The missing output_dir parameter and lack of error-handling details keep it from being fully complete, but it is sufficiently rich for an agent to invoke the tool correctly.

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 description explains pdf_file_path (accepted file types, Base64 reading), doc_name (optional, defaults to basename), and custom_field_keys (omit when no custom keys). However, output_dir is completely undocumented while schema coverage is 0%, leaving one of four parameters without semantic guidance.

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 verb+resource: 'extract structured invoice data from a document' and names the exact PDF4me endpoint. This clearly distinguishes it from sibling tools like process_receipt and process_universal_document by focusing on invoices.

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?

Provides clear operational context: when extracting invoice data, supply pdf_file_path, with optional doc_name and custom_field_keys. It does not explicitly name alternatives or exclusion criteria, but the invoice-specific scope makes usage clear; slight deduction for no 'when not to use' guidance.

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