Convert Markdown to PDF

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

The description adds that a sensible default stylesheet is applied and costs 1 credit, and returns PDF as an embedded resource. Annotations only provide openWorldHint=true, so description adds useful context but could disclose more behavioral details like error handling.

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-loading the action ('Render...PDF') and then adding key details. No redundant information, every word earns its place.

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?

Despite 18 parameters and no output schema, the description mentions return format and credit cost. However, it omits important context like error behavior, maximum input size, or support for advanced options like headers/footers. Adequate but with gaps.

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 100% schema description coverage, the baseline is 3. The description provides a high-level overview of parameters (CSS, layout options) but does not add meaningful detail beyond what the schema already provides for each parameter.

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 it 'Render a raw Markdown string to a PDF' – a specific verb and resource. It distinguishes from siblings like convert_html and convert_file by specifying Markdown as input and PDF as output.

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 when to use this tool (when converting Markdown to PDF) and mentions a default stylesheet, but lacks explicit guidance on when not to use it or alternatives (e.g., convert_html for HTML input).

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