markdown_to_pdf

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the primary conversion action. It does not mention side effects (e.g., overwriting existing files), output location behavior, formatting specificity, or any limitations (e.g., unsupported Markdown features). This lacks sufficient transparency for a tool without annotations.

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 that clearly conveys the essential purpose. There is zero wasted text, and it is front-loaded with the verb 'Convert' and the resource, making it immediately actionable.

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 file conversion tool, the description adequately covers the input, output, and format. The schema provides the parameter details, and the sibling tools clarify the domain. However, it lacks any mention of output_file handling or potential formatting nuances, which are minor gaps for a tool of this complexity.

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?

The input schema provides descriptions for both parameters (file and output_name), achieving 100% coverage. The tool description adds no parameter-specific meaning, but since the schema already handles this, the baseline score of 3 is appropriate. The schema's description for 'file' incorrectly mentions PDF instead of Markdown, but that is not the tool description's fault.

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 the tool's function with a specific verb ('Convert'), a concrete input resource ('Markdown (.md) file'), and the output format ('PDF'). It unambiguously distinguishes this tool from sibling converters like pdf_to_markdown (reverse direction), txt_to_pdf (different input), and json_to_pdf (different 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 provides no guidance on when to use this tool versus alternatives, no mention of prerequisites (e.g., whether the Markdown file must exist), and no exclusions. It simply states the action without contextualizing its place among similar conversion tools.

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