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 layout preservation and supports scanned images, but doesn't address rate limits, authentication requirements beyond the api_key parameter, file size limits, processing time, or error conditions. For a complex conversion tool with 11 parameters, this leaves significant behavioral gaps.

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 appropriately concise with two sentences: one stating the core functionality and one providing a reference link. It's front-loaded with the main purpose. The reference link is useful but could be integrated more seamlessly.

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 insufficient. It doesn't explain what the output looks like (text format, structure), error handling, performance characteristics, or limitations. The reference link helps but doesn't substitute for self-contained documentation.

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?

With 100% schema description coverage, the schema already documents all 11 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline of 3. However, it doesn't compensate with additional context about parameter interactions or usage patterns.

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 with specific verbs ('convert') and resources ('PDF and scanned images to text'), distinguishing it from siblings like pdf_to_csv or pdf_to_html. It explicitly mentions layout preservation, which is a key differentiator from plain text extraction tools.

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 implies usage for converting PDFs and scanned images to text, but doesn't explicitly state when to use this versus alternatives like pdf_make_searchable (for OCR) or find_text (for text extraction without conversion). The reference link provides external guidance but isn't integrated into the description itself.

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