pdfmux

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: automatic PDF type detection, selection of extraction methods, and return of confidence scores and warnings for limited extraction. However, it lacks details on error handling, performance characteristics (e.g., speed), or resource requirements, which are important for a conversion tool.

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 sized and front-loaded, with two sentences that efficiently convey core functionality and key behavioral aspects. Every sentence earns its place: the first states the purpose and automation, the second details output features, with zero waste or redundancy.

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 moderate complexity (conversion with automation), no annotations, and an output schema (which handles return values), the description is mostly complete. It covers purpose, automation, and output features but lacks parameter explanations and some behavioral details (e.g., error handling). With output schema reducing need for return value explanation, it's adequate but not fully comprehensive.

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 doesn't mention any parameters explicitly, failing to explain file_path (required input), format (default 'markdown'), or quality (default 'standard'). The baseline is 3 because the schema covers parameters structurally, but the description adds no semantic value beyond what the schema provides.

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 a PDF to AI-readable Markdown'), resource ('PDF'), and scope ('automatically detects PDF type and picks best extraction method'). It distinguishes from siblings like analyze_pdf (analysis vs conversion), batch_convert (single vs batch), extract_structured (generic extraction vs PDF-specific conversion), and get_pdf_metadata (metadata retrieval vs content conversion).

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 'automatically detects PDF type and picks best extraction method,' suggesting it handles various PDF formats intelligently. However, it doesn't explicitly state when to use this tool versus alternatives like batch_convert for multiple files or extract_structured for non-PDF documents, nor does it mention prerequisites or exclusions.

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