Import PDF Invoice or Receipt

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

With no annotations, the description carries the full burden of behavioral disclosure. It does state a key side effect: 'then record it as a transaction.' It also discloses what data it extracts (vendor, date, amounts, line items, GST). However, it does not mention failure modes, idempotency, required permissions, or any reversibility of the transaction recording.

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 three sentences long and every sentence adds value: the first identifies the action, the second lists the extracted data, and the third clarifies compatible document types. It is front-loaded with the primary purpose and contains no superfluous information.

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?

The tool has no output schema, so the description should help the agent understand what happens after invoking it. It states that it 'record[s] it as a transaction,' but does not explain the return value or what confirms success. Given the tool's moderate complexity (nested extracted_data object, 3 params) and rich schema coverage, the description is adequate but leaves some gaps about the operation's outcome.

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 coverage is 100%, so the baseline is 3. The description mentions fields like 'vendor, date, amounts, line items, and GST' that map to extracted_data fields, but the schema already describes these in detail. The description does not add meaningful syntactic or semantic detail beyond the schema, nor does it clarify the required 'file_path' or the optional 'document_type' beyond what the enum already indicates.

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 clearly states the tool's function: 'Read a PDF invoice or receipt and extract the transaction data' and then 'record it as a transaction.' It specifically names PDFs, distinguishing it from sibling tools like import_csv and import_spreadsheet, and enumerates document types (invoices, receipts, statements, bills).

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 clear context for when to use this tool: when you have a PDF document. It does not explicitly state exclusions or alternatives, such as 'use import_csv for CSV files,' but the mention of 'PDF invoice or receipt' and the list of document types implies the appropriate use cases. There is no explicit '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.