Convert Markdown into a clean, professionally formatted PDF and return a downloadable URL. Supports # / ## / ### headings, bold, code, - bullet lists, 1. numbered lists, and --- rules. Free tier: 30/hour; pass Authorization: Bearer for unlimited (buy a key at https://alpha-systems.net).
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | Document title, rendered as the top heading. | |
| markdown | Yes | Markdown body. | |
| page_size | No | Page size (default A4). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses rate limits, auth requirements, and the specific Markdown elements supported, which is useful. However, it does not mention error handling, what happens with unsupported Markdown, or whether the returned URL is persistent or temporary.
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 only two sentences, front-loading the core purpose in the first sentence and following with supported features and usage limits in the second. Every sentence adds value, with no filler or repetition of schema details.
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 the tool's simplicity (3 params, no output schema, no annotations), the description is largely complete: it specifies the return value (downloadable URL), usage limit, and supported Markdown subset. It could mention error handling or default behavior for omitted optional params, but the schema already covers defaults (e.g., page_size A4).
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 schema already describes all three parameters (markdown, title, page_size), so baseline is 3. The description adds meaningful detail by enumerating the supported Markdown syntax (headings, bold, code, lists, rules), which clarifies what the markdown parameter accepts and how it will be rendered. This goes beyond the schema's generic 'Markdown body.'
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 states a clear verb+resource: 'Convert Markdown into a clean, professionally formatted PDF and return a downloadable URL.' It explicitly contrasts with sibling tools like markdown_to_docx and markdown_to_html by targeting PDF output, making it easy to distinguish.
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 context for usage, including the free tier limit (30/hour) and that passing an Authorization: Bearer key enables unlimited use. It does not explicitly name alternatives or provide when-not-to-use guidance, but the PDF-focused purpose implies when to select it over other markdown converters.
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.
All six tools have clearly distinct purposes: converting markdown to different formats, merging/stamping PDFs, and checking recalls. No two tools are easily confused.
Most tools use a verb_noun pattern (generate_pdf, merge_pdfs, watermark_pdf, check_recalls), but markdown_to_docx and markdown_to_html use a different pattern (source_to_target). The inconsistency is minor and still readable.
With 6 tools, the count is reasonable for a document conversion utility. However, the inclusion of check_recalls feels out of place for a server named 'pdf', slightly diluting focus.
The tool set covers markdown-to-PDF and PDF merging/watermarking, but lacks PDF-to-other-format conversion, splitting, or editing. The recall checker is an unrelated gap filler. Core PDF workflows are partially covered.