data_excel_json

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

With no annotations, the description carries the burden. It discloses that json_to_excel writes to xlsx and requires output_path, and excel_to_json reads xlsx/csv, but lacks details on file overwrite behavior, error handling, or output JSON structure.

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?

Two sentences, front-loaded with the core purpose. All information is structured clearly with bullet-like separation of modes, 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 tool's moderate complexity and lack of output schema, the description adequately covers both directions and the required parameter. It does not detail output formatting or edge cases, but is sufficient for typical conversion tasks.

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 67%, so baseline is 3. The description adds the clarification that 'data' is a JSON array for json_to_excel and a file path for excel_to_json, slightly enhancing the 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 clearly states the tool's function as 'Excel/CSV ↔ JSON 转换' with specific verbs and resources. It distinguishes itself from sibling text/json conversion tools by explicitly targeting Excel/CSV files.

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 explains the two sub-modes (json_to_excel and excel_to_json) and specifies when output_path is required. It does not explicitly mention alternatives or exclusions, but the directional guidance is clear.

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