MD-PDF MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it states the tool performs a conversion and mentions customizable formatting, it doesn't disclose critical behavioral aspects like whether the operation modifies source files, what happens on failure, performance characteristics, or authentication requirements. The return statement only mentions success/failure messages without detailing error handling or output specifics.

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 well-structured with a clear purpose statement followed by organized parameter explanations. While efficient, the 'Returns' section could be more specific about message content. Some redundancy exists between the title-like first sentence and the detailed parameter descriptions, but overall it's appropriately sized for a 5-parameter tool.

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?

For a file conversion tool with 5 parameters, no annotations, and no output schema, the description provides adequate parameter semantics but lacks behavioral context about file system interactions, error conditions, and output handling. The absence of annotations means the description should cover more operational aspects, but it focuses primarily on parameter explanations rather than complete behavioral transparency.

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?

With 0% schema description coverage, the description compensates well by explaining all 5 parameters in the Args section. It clarifies working_dir as 'absolute path for file operations', markdown_file_path as 'relative to working_dir', output_filename's default behavior, size options with meanings ('s'=small/compact, etc.), and pdf_engine choices. This adds substantial value beyond the bare schema.

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 verb 'Convert' and specifies the resource 'Markdown file to PDF', distinguishing it from sibling tools like convert_pdf_to_markdown (reverse operation) and extract_text_from_pdf/get_pdf_info (different PDF operations). The mention of 'customizable formatting options' further clarifies the tool's capabilities beyond basic 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 through the stated purpose but doesn't explicitly guide when to use this tool versus alternatives like convert_markdown_to_pdf (which appears similar but might have different parameterization). No explicit when-not-to-use guidance or prerequisite information is provided, leaving some ambiguity about tool selection.

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