pdf_convert_to_markdown

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

No annotations, so description carries full burden. It mentions 'heuristics' which implies potential formatting imperfections but does not detail other behavioral aspects such as OCR support, image handling, or page orientation. Missing important limitations.

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 with no unnecessary words. However, it could be slightly expanded to include essential details without being verbose.

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 PDF-to-Markdown conversion, the description lacks details about the output format, handling of tables, images, lists, and limitations of heuristics. No output schema is provided to compensate.

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?

Both parameters have schema descriptions (100% coverage). The tool description does not add supplementary information about parameters beyond stating the overall purpose.

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 specifies the action (extract text and apply heuristics to format into Markdown) and the resource (PDF file). It clearly distinguishes from siblings like pdf_convert_to_text (plain text output) and pdf_extract_images (images only).

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?

No guidelines provided about when to use this tool versus alternatives like pdf_convert_to_text or image_ocr. The description does not mention prerequisites, file types, or scenarios where conversion might fail.

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