pdf_create_from_markdown

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

Annotations declare idempotentHint=true and readOnlyHint=false. The description adds valuable behavioral context not in annotations: specific Markdown elements supported (tables, code blocks, etc.) and the Roboto font constraint. It does not contradict annotations, though it omits file system side effects like overwrite behavior.

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?

Three well-structured sentences with zero waste: purpose declaration first, followed by capability enumeration, then implementation detail (font). Every sentence earns its place without redundancy.

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 rich input schema (8 well-documented parameters) and absence of an output schema, the description adequately covers the transformation logic (Markdown to PDF). It could be improved by noting file system write behavior, but the core functionality is complete.

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 adds semantic value by detailing what the markdown parameter can contain (headings, bold, italic, etc.) and noting the font choice, which helps users understand input capabilities beyond the schema's 'Markdown content' definition.

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 provides a specific verb (Create), resource (PDF), and distinct input format (Markdown) that clearly differentiates it from sibling tools like pdf_create and pdf_create_from_template. The mention of 'rich PDF' and specific formatting capabilities further clarifies the scope.

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 Markdown specification ('from Markdown content'), suggesting when to use this tool versus generic PDF creators. However, it lacks explicit when-to-use guidance, exclusions, or direct comparison to alternatives like pdf_create_from_template.

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