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 describes a read operation with parameters but lacks details on permissions, file access requirements, error handling, or output format. While it implies a non-destructive read, it does not explicitly state safety aspects like whether it modifies the file or has rate limits, leaving significant gaps for a tool with no annotation coverage.

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 front-loaded with the core purpose, followed by a structured list of parameters with clear explanations. Every sentence adds value without redundancy, and the format is efficient for quick comprehension, making it appropriately sized for the tool's complexity.

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 has an output schema, the description does not need to explain return values. However, with no annotations and 0% schema description coverage, it partially compensates with parameter semantics but lacks behavioral context like error cases or performance limits. It is adequate for a read operation but has clear gaps in safety and usage guidance.

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 schema description coverage is 0%, so the description must compensate. It adds meaningful semantics for all three parameters: path specifies file types (.ods, .xlsx), sheet_name clarifies behavior when None (reads first sheet), and max_rows defines a default (100). This goes beyond the bare schema, though it could provide more context on path validation or max_rows constraints.

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 ('Read data from') and resource ('LibreOffice Calc spreadsheet'), distinguishing it from sibling tools like read_document_text or get_document_info that handle different document types or operations. It precisely defines what the tool does without being vague or tautological.

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 read_document_text (for text documents) or get_document_info (for metadata). It mentions default behavior for sheet_name and max_rows but does not specify use cases, prerequisites, or exclusions, leaving the agent to infer usage from context alone.

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