Compress a PDF file to reduce its size. Returns a download URL for the compressed file. Free tier: 500 calls/month.
| 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?
With no annotations, the description carries the behavioral transparency burden. It adds that the tool returns a download URL and has a rate limit. However, it does not disclose file size limitations, whether the original file is modified, or URL expiration. This is incomplete but not misleading.
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 extremely concise: three sentences that front-load the core purpose, result, and a usage constraint. Every sentence adds value, with no verbosity.
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 is adequate but incomplete. It does not clarify the relationship between file_url and file_base64 (they are alternatives) or specify the response format beyond a download URL. Additional context would improve completeness.
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 100%, so parameters are well documented. The tool description adds no additional meaning beyond the overall purpose. Baseline of 3 is appropriate as the description does not enhance parameter understanding beyond what the schema already provides.
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 compresses a PDF to reduce size and returns a download URL. It uses a specific verb 'compress' and resource 'PDF file'. It distinguishes from siblings like pdf_to_excel (conversion) and others, making the purpose unmistakable.
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 does not provide guidance on when to use this tool versus alternatives, such as pdf_to_excel or extract_invoice_data. It mentions a free tier limit (500 calls/month) but lacks explicit when-to-use or when-not-to-use context.
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.
