Create PDF from Markdown

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

Annotations already indicate this is not read-only and is idempotent; the description adds a valuable behavioral disclosure: inline decoration markers are stripped and text is rendered plain in a single font. This is non-obvious and helps set expectations, though it does not detail file output behavior or failure modes.

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 two sentences, front-loaded with the core purpose, and then adds a compact list of supported features plus an important behavioral caveat. Every sentence earns its place with no redundancy or filler.

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 detailed schema descriptions for all 13 parameters, the description does not need to repeat them. It covers the supported Markdown feature set and a key rendering behavior, which is sufficient for invocation. A small gap is the absence of any guidance about output modes or when to use sibling PDF creation tools, but the schema fills most operational details.

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 100%, so the parameters are already well documented individually. The description adds no parameter-specific meaning beyond the schema; it only gives a general overview of Markdown support. Baseline 3 is appropriate because the schema carries the burden.

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 states a specific verb and resource: 'Create a PDF from Markdown,' and enumerates the supported Markdown constructs (headings, lists, code blocks, tables, etc.). It is clear about what the tool does, though it does not explicitly differentiate itself from the sibling tools create_text_pdf or create_table_pdf beyond implying Markdown input.

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: use this tool when you have Markdown content and want a PDF. It lists supported elements, which gives some scope, but it gives no explicit guidance about when to choose this over create_text_pdf or create_table_pdf, and no mention of limitations or exclusions.

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