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. It states the conversion action but lacks critical details: whether this is a read-only operation, if it modifies the original PDF, what permissions are needed, how errors are handled, or what the output format entails (e.g., markdown structure, quality of conversion). For a tool with no annotation coverage, this is a significant gap.

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 a single, efficient sentence with zero waste. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration. Every word earns its place, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete for a file conversion tool. It doesn't explain what the markdown output looks like (e.g., formatting, metadata), potential limitations (e.g., complex PDFs, images within PDFs), or error conditions. With no structured data to compensate, the description should provide more context about the tool's behavior and results.

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 description coverage is 100%, with the single parameter 'filepath' fully documented in the schema as 'Absolute path of the PDF file to convert'. The description adds no additional parameter semantics beyond what the schema provides, such as file size limits, supported PDF versions, or path format examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 a specific verb ('Convert') and resource ('a PDF file to markdown'), making it immediately understandable. It distinguishes from most siblings by specifying PDF input, though it doesn't explicitly differentiate from other file conversion tools like docx-to-markdown or pptx-to-markdown beyond the file type.

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, pptx-to-markdown), there's no indication of when PDF conversion is appropriate or what distinguishes it from other conversion tools. No prerequisites or exclusions are mentioned.

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