Convert a PDF (tables, statements, reports) to an Excel file. Returns a download URL. Requires Premium tier or above.
| Name | Required | Description | Default |
|---|---|---|---|
| file_url | No | HTTPS URL of the file to process (the server downloads it) | |
| filename | Yes | Filename with extension, e.g. invoice.pdf | |
| file_base64 | No | Base64-encoded file content (alternative to file_url; max 15MB decoded) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose all behavioral traits. It mentions the Premium requirement and return of a download URL, but lacks details on processing limits, error handling, or potential side effects (e.g., file storage). This leaves the agent with incomplete understanding of 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 sentences, front-loaded with action, no unnecessary words. Every sentence adds value: what the tool does, what it returns, and a requirement.
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?
Given 3 parameters and no output schema, the description covers the output (download URL) and a requirement (Premium tier). However, it lacks details on file size limits, conversion accuracy, or failure modes. Adequate but not comprehensive.
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% with each parameter described (file_url, filename, file_base64). The description adds no extra parameter semantics beyond the schema. Baseline score of 3 is appropriate as schema does the heavy lifting.
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?
Description clearly states it converts PDF to Excel, specifying types of PDFs (tables, statements, reports) and that it returns a download URL. This distinguishes it from sibling tools like compress_pdf or extract_invoice_data, which serve different purposes.
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 one usage constraint (requires Premium tier), but does not guide when to use this tool versus alternatives like extract_invoice_data or parse_bank_statement. No exclusions or 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.
Add one secure layer between your agents and this server.
Each tool targets a distinct document processing task (compression, fraud detection, invoice extraction, statement parsing, conversion, reconciliation, GST validation) with clear descriptions that avoid overlap.
All tool names follow the verb_noun snake_case pattern (e.g., compress_pdf, validate_gstin), providing a predictable and uniform naming convention.
Seven tools cover the core capabilities for a PDF/document magic service focused on financial documents, balancing breadth without being overwhelming or sparse.
The set addresses key workflows (compress, convert, extract, parse, validate, reconcile), but misses general OCR or merge/split features. For the financial niche, it is nearly complete.
