PDF.co MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions conversion but doesn't describe what happens during processing (OCR for scanned images, potential rate limits, authentication requirements beyond the optional parameters, or output characteristics). The external reference link suggests additional documentation exists elsewhere, but the description itself lacks essential behavioral context for a conversion tool with 11 parameters.

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 with just two sentences. The first sentence states the core purpose, and the second provides a reference link. There's zero waste or redundancy, making it appropriately sized and front-loaded with the essential 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?

For a complex conversion tool with 11 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the XML output contains, how conversion errors are handled, whether this is a synchronous or asynchronous operation, or any performance characteristics. The external reference suggests missing information exists elsewhere, but the description itself lacks completeness for effective tool selection and invocation.

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 the schema already documents all 11 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema. The baseline score of 3 reflects that the schema does the heavy lifting for parameter documentation, and the description doesn't compensate or add additional semantic context.

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 purpose: 'Convert PDF and scanned images to XML format.' This specifies the verb (convert) and resources (PDF, scanned images) with the target format (XML). However, it doesn't differentiate from sibling tools like 'pdf_to_csv', 'pdf_to_html', or 'pdf_to_json' which perform similar conversions to different formats.

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 provides no guidance on when to use this tool versus alternatives. With multiple PDF conversion siblings (pdf_to_csv, pdf_to_html, pdf_to_json, pdf_to_text, etc.), there's no indication of when XML output is preferred over other formats. The reference link to external documentation doesn't substitute for explicit usage guidance within the description itself.

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