markdown_to_pdf

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only states the conversion action without mentioning side effects, output file handling, overwrite behavior, required permissions, or any errors. This is a significant gap for a tool that creates a file on the filesystem.

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 one short sentence with zero filler words. It front-loads the core purpose without extraneous detail, making it highly concise. It is an efficient use of words, not under-specified to the point of being meaningless (unlike a single verb like 'process').

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?

This tool has 5 parameters, no annotations, and an output schema, but the description is too sparse to provide complete context. It does not explain how parameters interact, what the output schema contains, or any prerequisites. For a nontrivial tool with multiple configurable options, the description is insufficient.

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%, and the description adds no parameter-specific meaning. While parameter names like margin, font_size, and page_size are somewhat self-explanatory, the description does not explain formats, units, or how output_path defaults to null. It fails to compensate for the lack of schema descriptions.

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 tool converts Markdown files to PDF format, using a specific verb ('Convert') and resource ('Markdown file' to 'PDF format'). It distinguishes itself from sibling tools like pdf_to_markdown (which does the reverse) and list_supported_formats/validate_file by stating the exact conversion direction.

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?

Usage is implied by the conversion direction: use this when you need to turn Markdown into PDF. However, the description does not explicitly mention alternatives or exclusions, such as when to prefer pdf_to_markdown or check supported formats first. It gives no explicit when-to-use guidance beyond the basic purpose.

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