convert_spreadsheet

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

With no annotations, the description must carry behavioral disclosure, but it only makes the blanket claim that formulas, styles, and multiple worksheets are preserved. This is not uniformly true across CSV/TSV/JSON/HTML outputs and conflicts with the schema's include_formulas option, which says computed values are used unless formulas are explicitly kept. It also does not mention overwriting, dependency, or output-path 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?

A single, densely informative sentence that front-loads the verb, resource, and supported formats before the key preservation guarantees. No filler or redundancy.

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?

The tool has nested options, no output schema, and no annotations, and it sits among many sibling converters. The description omits how output_path behaves when omitted, format-specific limitations, formula handling details, and any dependencies or side effects, leaving an agent under-informed for correct invocation.

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 coverage is roughly 75% and all visible parameter properties have descriptions, so the schema does most of the work. The description adds no parameter-level detail beyond listing formats, but it does not conflict with the schema; a baseline 3 is appropriate.

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 names the specific verb '转换' and resource '电子表格', and lists the supported formats (XLSX/XLS/ODS/CSV/TSV/JSON/HTML). It also names distinctive preservation behavior (formulas, styles, multiple sheets), which differentiates it from sibling generic converters like convert_data or convert_document.

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 format list and '电子表格转换' clearly indicate a spreadsheet-conversion context, but the description does not explicitly state when to choose this tool over convert_data or convert_document, nor does it give exclusions or alternatives. Usage rules are implied rather than stated.

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