pdf_to_markdown

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

The description only restates the basic conversion without disclosing behavior around image extraction, formatting preservation, error handling, or output characteristics. With no annotations, this leaves the agent uninformed about edge cases and side effects.

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 concise sentence, but it is under-specified for a tool with four parameters. While it does not waste words, it lacks structured information needed for effective tool invocation.

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 has four parameters, an output schema, and no annotations, the description is insufficiently complete. It does not cover parameter behavior, side effects, or output characteristics, making it barely adequate for an agent to understand the full context.

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 description does not mention any of the four parameters (pdf_path, output_path, extract_images, preserve_formatting) or their semantic meaning. Since schema description coverage is 0%, the description fails to compensate for the lack of parameter guidance.

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 action (convert) and the resource transformation (PDF to Markdown), which is specific and distinguishes it from the sibling tools like markdown_to_pdf and list_supported_formats.

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 implicitly conveys when to use this tool (when you need Markdown from a PDF) but does not explicitly mention alternatives or exclusions. It provides the core purpose but lacks direct comparison to siblings.

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