LibreOffice MCP Tools

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

With no annotations, the description carries full burden. It discloses the LibreOffice dependency and supported formats, which are useful behavioral traits. However, it doesn't cover critical aspects like whether the export modifies the original document, error handling, or output file behavior beyond the default path hint.

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?

Three sentences with zero waste: first states core purpose, second lists supported formats, third gives prerequisite. Each sentence adds essential information, and the description is appropriately sized and front-loaded.

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?

For a tool with no annotations and no output schema, the description covers purpose, formats, and prerequisite well. However, it lacks details on mutation behavior (e.g., whether original document is altered), error cases, or output specifics, leaving some gaps for a tool that performs file operations.

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 fully documents parameters. The description adds no parameter-specific semantics beyond implying format options (listed in schema enum) and a default output path behavior, which is partially covered in schema. Baseline 3 is appropriate as schema does the heavy lifting.

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 ('Export a document to a different format') and resource ('document'), distinguishing it from siblings like document_convert (which might convert without export) or document_save (which saves in original format). The mention of LibreOffice adds technical specificity.

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 by specifying supported formats and a prerequisite (LibreOffice must be installed), but lacks explicit guidance on when to use this tool versus alternatives like document_convert or document_save. No exclusions or sibling comparisons are provided.

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