excel_export_html

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description details the conversion process, delegating to an internal function, and lists multiple error types (file not found, unsupported format, missing LibreOffice, export failure). It does not mention if the tool is read-only or if it overwrites existing files, which are minor 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 well-structured with clear sections (main description, Args, Returns, Raises). Each sentence adds value, and it is appropriately detailed without being verbose.

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 (external dependency, conversion), the description covers the main aspects: purpose, parameters, return value, and error handling. It lacks details on HTML format or performance limitations, but overall it is fairly comprehensive.

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's Args section is crucial. It provides clear semantics for all three parameters: path (existing .xlsx), output (target path with parent directory creation), and folder (optional base folder). This fully compensates for the lack of schema descriptions.

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 explicitly states 'Convert a .xlsx file to HTML via LibreOffice headless', providing a specific verb and resource. It also differentiates from the Word variant, clarifying the unique method used.

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 mentions the Word variant and notes that this tool always uses LibreOffice, implying its specific use case. However, it does not explicitly list sibling tools or provide explicit when-to-use vs. alternatives, leaving some ambiguity.

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