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 of behavioral disclosure. It mentions 'automatic refresh capabilities' but doesn't explain what this entails, such as how often refreshes occur or what triggers them. Critical details like permissions required, whether the session is persistent, or potential side effects are missing, leaving significant gaps in understanding the tool's behavior.

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 concise and well-structured, with a clear purpose statement followed by a brief parameter list. Each sentence serves a purpose, and there's no unnecessary verbosity, 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 the tool's complexity (creating a live editing session) and the presence of an output schema, the description is moderately complete. It covers the basic purpose and parameters but lacks details on behavioral aspects like session management or refresh behavior. The output schema likely handles return values, so the description doesn't need to explain those, but it should provide more context on usage and limitations.

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 minimal semantics beyond the input schema, which has 0% coverage. It briefly explains 'path' as 'Path to the document for live editing' and 'auto_refresh' as 'Whether to enable automatic refresh detection', but this doesn't fully compensate for the lack of schema descriptions. For example, it doesn't specify the format of 'path' or what 'automatic refresh detection' means in practice, leaving parameters partially unclear.

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 ('Create a live editing session') and the resource ('document for live editing'), specifying the tool's purpose. However, it doesn't distinguish this tool from potential siblings like 'create_document' or 'watch_document_changes', which might involve similar document operations but with different functionalities.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, such as whether the document must exist or be accessible, and doesn't mention any sibling tools like 'create_document' or 'watch_document_changes' that might serve overlapping purposes.

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