LibreOffice MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'refresh signal' and 'reload a document', implying a read-only or update operation, but fails to detail critical aspects like whether this requires LibreOffice to be running, if it affects unsaved changes, error handling, or response behavior. This leaves significant gaps for a tool interacting with external software.

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 brief and front-loaded with the main purpose in the first sentence, followed by parameter details. It avoids unnecessary words, though the structure could be slightly improved by integrating the parameter explanation more seamlessly.

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 (interacting with LibreOffice), lack of annotations, and presence of an output schema (which reduces need to explain returns), the description is minimally adequate. It covers the basic action and parameter but misses important contextual details like dependencies on LibreOffice state or error scenarios, making it incomplete for safe use.

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 context for the single parameter 'path' by specifying it as 'Path to the document that should be refreshed', which clarifies its role beyond the schema's basic type. With 0% schema description coverage and only one parameter, this compensates adequately, though it could include format examples (e.g., file paths).

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 ('Send a refresh signal') and the resource ('to LibreOffice to reload a document'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'open_document_in_libreoffice' or 'watch_document_changes', which might involve similar document-handling operations.

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 lacks context such as prerequisites (e.g., document must be open in LibreOffice), exclusions, or comparisons to siblings like 'open_document_in_libreoffice' for initial loading or 'watch_document_changes' for monitoring updates.

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