excel_to_csv

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

No annotations are present, yet the description only states a straightforward conversion with no disclosure of side effects, file size limits, or performance characteristics. For a transformation tool, more behavioral details would be beneficial.

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 short, front-loaded with the purpose, and structured using a docstring format. Every sentence contributes value, though the Args/Returns section could be slightly more streamlined.

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 simplicity and the presence of an output schema, the description adequately covers the core functionality and parameters. It lacks only minor details like potential limits or edge cases.

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 0%, but the description adds meaningful semantics to all three parameters: explains base64 encoding, 0-based sheet index, and default delimiter. This goes well beyond the schema's bare names and types.

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 action ('Extract data') and the resource ('an Excel sheet'), with the output format ('CSV text'). It effectively distinguishes from sibling tools like excel_to_json or csv_to_excel.

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 lists arguments but does not provide explicit guidance on when to use this tool versus alternatives (e.g., excel_to_json). Usage is implied but not elaborated.

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