PDF.co MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions conversion capabilities and references external documentation, but doesn't describe critical behaviors like rate limits, authentication requirements beyond optional parameters, error handling, or output format details. The reference link hints at more information but isn't self-contained.

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 efficiently structured in two sentences: the first states the core purpose, the second provides a reference link. There's no wasted text, though the reference link could be considered slightly extraneous if the description were fully self-contained.

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, how errors are handled, performance characteristics, or limitations. The reference link partially compensates but doesn't provide complete contextual understanding within the description itself.

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 additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for adequate coverage through structured data alone.

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 XLS format'), and distinguishes it from sibling tools like 'pdf_to_csv', 'pdf_to_xlsx', and 'pdf_to_text' by specifying the exact output format (Excel 97-2003).

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 context through the reference link and mentions 'scanned images', suggesting OCR capabilities, but doesn't explicitly state when to use this tool versus alternatives like 'pdf_to_xlsx' or 'pdf_to_csv'. No explicit exclusions or prerequisites are provided.

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