LibreOffice MCP Tools

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. It effectively describes key behavioral traits: it 'Creates a new file; original is not modified' (clarifying non-destructive nature), specifies the underlying technology ('using LibreOffice CLI'), and states a system requirement ('LibreOffice must be installed'). This covers mutation behavior, safety, and prerequisites, though it lacks details on error handling or performance limits.

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 appropriately sized and front-loaded, with three concise sentences that each earn their place: the first states the core purpose, the second clarifies behavior and provides usage examples, and the third specifies a prerequisite. There is zero waste or redundancy, making it highly efficient and easy to parse.

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 moderate complexity (file conversion with system dependencies), no annotations, and no output schema, the description is largely complete. It covers purpose, behavior, usage examples, and prerequisites. However, it does not describe the return value or potential error cases, which would be helpful for an agent invoking the tool without an output schema.

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 description coverage is 100%, so the schema already documents all three parameters (filePath, format, outputPath) with descriptions and an enum for format. The description does not add any parameter-specific semantics beyond what the schema provides, such as explaining format constraints or outputPath behavior. The baseline score of 3 is appropriate given the comprehensive schema coverage.

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 specific action ('Convert a document file to a different format') and resource ('document file'), using the verb 'Convert' with the tool name 'document_convert'. It distinguishes from siblings like 'document_export' by specifying the LibreOffice CLI method and providing concrete examples of conversions (DOC→DOCX, DOCX→PDF, etc.).

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 clear context for when to use this tool ('Useful for: DOC→DOCX, DOCX→PDF, XLSX→CSV, etc.') and mentions a prerequisite ('LibreOffice must be installed'). However, it does not explicitly state when not to use it or name specific alternatives among the sibling tools, such as 'document_export' which might serve a similar purpose.

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