LibreOffice MCP Server

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

With no annotations provided, the description carries the full burden. It discloses that the tool opens a document in LibreOffice GUI for live viewing, which implies a user interface interaction and potential resource usage. However, it doesn't mention behavioral traits like whether it launches a new instance, handles errors for invalid paths, or requires LibreOffice installation, leaving gaps in understanding the tool's operation.

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 front-loaded with the core purpose in the first sentence, followed by a structured 'Args:' section that efficiently documents parameters. Every sentence adds value without redundancy, making it appropriately sized and easy to parse quickly.

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 (2 parameters, no annotations, but has an output schema), the description is mostly complete. It covers the purpose and parameters adequately, but since an output schema exists, it doesn't need to explain return values. However, it could benefit from more behavioral context, such as error handling or prerequisites, to be fully comprehensive.

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 0%, so the description must compensate. It adds meaning by explaining 'path' as 'Path to the document to open' and 'readonly' as 'Whether to open in read-only mode (default: False)', which clarifies the purpose and default behavior beyond the bare schema. However, it doesn't detail path format constraints or read-only implications, keeping it from a perfect score.

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 ('Open a document in LibreOffice GUI for live viewing'), identifies the resource ('document'), and distinguishes it from siblings like 'create_document' or 'read_document_text' by emphasizing GUI interaction and live viewing. It provides a verb+resource combination that is precise and unambiguous.

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 for opening documents in LibreOffice GUI, which suggests it's for interactive viewing rather than batch processing or conversion (contrasted with siblings like 'batch_convert_documents' or 'convert_document'). However, it lacks explicit guidance on when not to use it or direct alternatives, such as 'refresh_document_in_libreoffice' for already open documents.

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