Convert DOCX, XLSX, or PPTX files to PDF with LibreOffice when available, specifying an input path and optional output path or overwrite setting.
Convert an XLSX, DOCX, or PPTX file to PDF using LibreOffice when available.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Absolute path or path relative to the server working directory | |
| overwrite | No | ||
| outputPath | No | Absolute path or path relative to the server working directory |
Changes observed during successful MCP inspections.
v0.10.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is partly covered. The description adds the LibreOffice dependency, which is genuine behavioral context, but omits what happens when LibreOffice is unavailable, how 'overwrite' interacts with existing files, and where output lands by default.
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?
A single tight sentence with the operation front-loaded and no filler. It is efficient, though the brevity arguably costs it needed detail rather than serving conciseness.
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?
With no output schema and a destructive mutation, the description should cover overwrite semantics and failure behavior, which it does not. The 'when available' clause is a partial acknowledgment of a fallback path but leaves the agent without enough to act correctly in edge cases.
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 only 67%, and the undocumented parameter is 'overwrite' — the one most tied to the destructiveHint. The description mentions no parameter at all, so it fails to compensate for the coverage gap on a mutation-relevant flag.
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?
States a specific verb (convert) with explicit source formats (XLSX, DOCX, PPTX) and target (PDF), which is clearly actionable. However, it never distinguishes itself from the sibling office_export_pdf, which an agent could easily confuse with this tool.
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?
There is no guidance on when to use this versus office_export_pdf or office_convert alternatives, nor any stated prerequisites. The only hint ('when available') gestures at a condition but does not tell the agent how to react to its absence.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.