LibreOffice MCP Server

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It mentions batch conversion but doesn't disclose whether it overwrites existing files, handles errors (e.g., unsupported formats), requires specific permissions, or has rate limits. The description adds minimal context beyond the basic operation, leaving significant gaps for a mutation tool.

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: the first sentence states the core purpose, followed by a bulleted list of parameters with clear explanations. Every sentence earns its place without redundancy, making it 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 complexity (batch file conversion with 4 parameters), no annotations, and an output schema (which reduces need to explain returns), the description is moderately complete. It covers parameters well but lacks behavioral context (e.g., error handling, file overwrites). For a mutation tool with no annotations, it should do more to guide safe usage.

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 description adds meaningful semantics beyond the input schema, which has 0% description coverage. It explains 'source_dir' as 'Directory containing source documents', 'target_dir' as where converted documents are saved, 'target_format' as the target format, and 'source_extensions' with a default. This compensates well for the schema's lack of descriptions, though it doesn't specify format examples or extension syntax.

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 purpose: 'Convert multiple documents in a directory to a different format' - a specific verb ('convert') and resource ('multiple documents in a directory'). It distinguishes from siblings like 'convert_document' (single document) and 'create_document' (creation vs conversion). However, it doesn't explicitly mention what happens to unconverted files or error handling, keeping it from a perfect score.

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. It doesn't mention prerequisites (e.g., directory existence, permissions), when to use 'convert_document' for single files, or how it differs from siblings like 'merge_text_documents' or 'open_document_in_libreoffice'. Usage is implied by the name but not explicitly stated.

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