pdfmux

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

With no annotations provided, the description carries the full burden. It discloses the batch processing behavior and return format (summary with per-file results), which is useful. However, it omits critical behavioral traits such as error handling, performance expectations (e.g., timeouts), or permissions required, leaving gaps for a tool that performs file operations.

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 two sentences, front-loaded with the core action and followed by return information. Every sentence adds value without redundancy, making it highly efficient and well-structured 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 tool's complexity (batch file conversion), no annotations, and an output schema (which handles return values), the description is reasonably complete. It covers the main action and output, but lacks details on behavioral aspects like error handling or parameter usage, which could enhance completeness for this type of operation.

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 0%, so the description must compensate. It mentions 'directory' implicitly but does not explain the 'quality' parameter or provide any details on parameter semantics (e.g., what 'standard' quality entails). The description adds minimal value beyond the schema, failing to address the coverage gap adequately.

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 specific action ('Convert all PDFs in a directory to Markdown') and distinguishes it from siblings like 'convert_pdf' (single file) and 'analyze_pdf' (analysis rather than conversion). It specifies the resource (PDFs in a directory) and output format (Markdown), making the purpose unambiguous.

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 batch conversion of PDFs to Markdown, which differentiates it from single-file conversion ('convert_pdf') and analysis tools ('analyze_pdf', 'get_pdf_metadata'). However, it lacks explicit guidance on when to use this tool versus alternatives like 'extract_structured' or any exclusions (e.g., non-PDF files).

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