pdf-to-markdown

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'convert' implies a transformation operation, the description doesn't disclose important behavioral traits such as whether the conversion is lossy, what markdown format is produced, whether it handles scanned PDFs with OCR, or any error conditions. This leaves significant gaps in understanding how the tool behaves.

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 at just 5 words, with zero wasted language. It's front-loaded with the core purpose and contains no unnecessary information, making it efficient for quick understanding.

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 complexity of file format conversion and the lack of both annotations and output schema, the description is insufficiently complete. It doesn't explain what the tool returns (e.g., markdown text, file path to converted content), doesn't mention limitations or requirements, and provides no context about the conversion quality or supported PDF features.

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 input schema has 100% description coverage, with the single parameter 'filepath' clearly documented as requiring an absolute path. The description doesn't add any meaningful parameter semantics beyond what the schema already provides, so it meets the baseline score of 3 for high schema coverage.

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 as converting a PDF file to markdown, which is a specific verb (convert) and resource (PDF file). It distinguishes itself from siblings by focusing on PDF files specifically, though it doesn't explicitly contrast with other conversion tools like docx-to-markdown or image-to-markdown.

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 sibling tools for converting different file types to markdown (e.g., docx-to-markdown, image-to-markdown), there's no indication of when PDF conversion is appropriate or what distinguishes it from other conversion methods.

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