markdown_to_pdf

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

The annotations already provide readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral context by stating the result is a URL to a downloadable PDF, and mentions supported Markdown features. It does not disclose limitations such as file size, async behavior, or URL expiry, but nothing contradicts the read-only hint.

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 long, front-loads the core purpose, and contains no filler or redundant restatement. Every sentence contributes useful information.

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 simple conversion tool with fully documented parameters and a URL return value described, this is mostly complete. The only gap is the absence of practical caveats like file-size limits, processing time, or how long the returned URL remains valid, which could matter to an agent invoking the tool.

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 schema already documents all five parameters. The description adds context around GFM tables, code blocks, and custom page sizes, which helps clarify intended usage, but it does not meaningfully expand on individual parameter semantics beyond the 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 uses a specific verb ('Convert') and names both input and output resources: Markdown content to a downloadable PDF document. It also distinguishes itself from closely related siblings like html_to_pdf and markdown_to_html by clearly stating the conversion direction and output format.

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 the use case clearly: use this tool when you have Markdown and need a PDF. However, it does not explicitly compare with alternatives like html_to_pdf or markdown_to_html, nor does it state when not to use this tool.

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