pdf_create_from_markdown

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

Annotations provide idempotentHint=true and destructiveHint=false. The description adds value by detailing supported Markdown features (CommonMark + GFM elements), which helps the agent understand output fidelity and constraints. However, it does not disclose behavior for unsupported elements.

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 a single concise sentence followed by a list of supported features. It is front-loaded with the main action and contains no redundant 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?

Given the tool's complexity (Markdown to PDF with multiple features), the description covers the supported syntax adequately. No output schema exists, but the tool's purpose (file creation) implies a file at outputPath. Missing details on return values or error handling reduce completeness slightly.

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 coverage is 100% with descriptions for all parameters. The description does not add further explanation beyond what the schema provides, so baseline score 3 is appropriate.

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 'Create a rich, high-fidelity PDF from Markdown', specifying the verb (create), resource (PDF), and source format (Markdown). It also lists supported syntax elements, distinguishing this tool from siblings like pdf_create (generic) and pdf_create_from_template.

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 when Markdown content is available but lacks explicit guidance on when to use this tool versus alternatives (e.g., pdf_create for other inputs). No when-not-to-use or alternative references are provided.

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