LibreOffice MCP Tools

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 effectively describes key behaviors: it's a read operation (implied by 'Read'), returns data in structured formats, supports pagination when range is omitted, and emphasizes token efficiency. However, it doesn't mention rate limits, authentication needs, or error handling, leaving some 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 front-loaded with the core purpose, followed by usage guidelines and efficiency tips. Every sentence earns its place: the first states what it does, the second explains output formats, the third clarifies range usage, and the fourth advises on token efficiency. No wasted words.

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 complexity (6 parameters, no output schema, no annotations), the description is largely complete: it covers purpose, usage, output formats, and parameter guidance. However, it lacks details on error cases, authentication, or exact return structure, which could be helpful for a read tool with multiple parameters.

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 100%, so the baseline is 3. The description adds value by explaining the semantics of the 'range' parameter (e.g., 'A1:D10' for specific cells, omitting for paginated full sheet) and implicitly clarifying 'limit' and 'offset' through pagination context. It doesn't detail all parameters but enhances understanding beyond the schema.

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 with specific verbs ('Read a range of cells') and resources ('from a spreadsheet sheet'), distinguishing it from siblings like spreadsheet_get_formulas (formulas only) or spreadsheet_set_range (write operation). It explicitly mentions the output formats (JSON and markdown table), which further clarifies its function.

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 explicit guidance on when to use this tool vs. alternatives: it advises specifying a range for token efficiency rather than reading the whole sheet, and mentions omitting the range for paginated full sheet access. It also distinguishes from siblings by focusing on reading cell data (not formulas, metadata, or writing).

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