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 states the conversion action but doesn't describe what happens during conversion (e.g., formatting changes, potential data loss, supported source formats, error handling, or performance implications). For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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: a clear purpose statement followed by a bulleted list of parameters. Every sentence earns its place, with no redundant information. However, it could be more front-loaded with critical details like supported source formats.

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 (3 parameters, mutation operation), no annotations, but with an output schema present, the description is partially complete. It covers the basic action and parameters but lacks details on behavioral traits, usage context, and error handling. The output schema mitigates the need to describe return values, but other gaps remain.

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 lists all three parameters with brief explanations, but schema description coverage is 0%, so the schema provides no additional details. The description adds basic semantics (e.g., 'Path to the source document'), but doesn't elaborate on format constraints, path requirements, or the 'etc.' in target_format. It compensates somewhat for the schema gap but remains minimal.

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 tool's purpose: 'Convert a document to a different format.' It specifies the verb ('convert') and resource ('document'), but doesn't explicitly differentiate from siblings like 'batch_convert_documents' or 'merge_text_documents' beyond the singular vs. batch distinction. The purpose is clear but lacks sibling-specific differentiation.

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 doesn't mention sibling tools like 'batch_convert_documents' for multiple files, 'create_document' for new documents, or 'read_document_text' for extraction without conversion. There's no context about prerequisites, file types, or when-not-to-use scenarios.

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