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 adds useful context about supported formats and automatic conversion via LibreOffice, but does not mention permissions, rate limits, or error handling. It adequately describes the core behavior without contradictions, but lacks depth on operational traits.

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 main purpose in the first sentence, followed by supporting details in a structured list of formats and conversion notes. Each sentence adds necessary information without redundancy, making it efficient and well-organized.

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 (opening files with format support), no annotations, and no output schema, the description is mostly complete. It covers purpose, usage, and behavioral aspects like conversion, but could improve by detailing return values or error cases, though the output is implied as a docId handle.

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 has 100% description coverage for the single parameter 'filePath', so the baseline is 3. The description adds value by implying the parameter is used to specify a document file for opening, though it does not provide additional syntax or format details beyond the schema's description of 'Absolute or relative path'.

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 action ('Open a document file') and the resource ('document file'), specifying it returns a docId handle for use with other tools. It distinguishes from siblings by focusing on opening files rather than creating, converting, or manipulating documents, making the purpose specific and well-defined.

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 by listing supported file formats and mentioning automatic conversion for legacy formats, which helps users know when this tool is applicable. However, it does not explicitly state when to use alternatives like document_convert or document_create, missing explicit exclusions or comparisons with siblings.

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