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 only minimally addresses behavior. It mentions 'insert' implies mutation but doesn't disclose critical traits like whether changes are saved automatically, permission requirements, error handling, or side effects on document formatting. This leaves 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 efficiently structured with a clear purpose statement followed by a bullet-point list of parameters. Every sentence earns its place without redundancy, making it easy to scan and understand 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 a mutation tool with no annotations, 3 parameters, and an output schema (which reduces need to describe returns), the description is minimally adequate. It covers the basics but lacks depth on behavioral context, error conditions, and integration with sibling tools, leaving room for improvement.

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 lists all three parameters with brief explanations, adding value beyond the bare schema. However, it doesn't elaborate on format details (e.g., path syntax, text encoding, position enum meanings beyond listing them), keeping it at a baseline level.

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 verb ('Insert text') and resource ('into a LibreOffice Writer document'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'merge_text_documents' or 'create_document', which prevents 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 like 'create_document' or 'merge_text_documents'. It lacks context about prerequisites (e.g., document must exist) or exclusions, offering only basic parameter explanations without usage scenarios.

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