Convert Excel To Csv

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

With no annotations, the description carries the full behavioral disclosure burden. It usefully reveals that the tool expects Base64-encoded input and produces CSV output, but it omits details such as how multiple worksheets are handled, whether formulas are evaluated, output encoding, size limits, or the exact return format.

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 a single sentence with no filler. The main action, input format, and output format are all front-loaded, making it easy to parse quickly.

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?

For a one-parameter conversion tool, the description is close to sufficient: an agent can construct a valid request. However, the absence of annotations and an output schema means the return format and edge-case behavior (multi-sheet files, file size, encoding) remain unspecified, making this a minimal-viable rather than fully complete definition.

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 must clarify the parameter. It adds meaning by identifying spreadsheet_b64string as Base64-encoded Excel content, going beyond the bare string type. Still, much of this is implied by the parameter name, and accepted Excel formats or constraint details are not specified.

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 states a specific verb and resource: converting Excel content to CSV format. This clearly differentiates it from convert_excel_to_json and the more generic convert_spreadsheet and save_spreadsheet_as siblings, and it also identifies the input representation (Base64 string).

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 intended use is implied by the output target: choose this tool when CSV output is needed from Base64-encoded Excel content. However, it does not explicitly contrast itself with sibling converters or state when an alternative such as convert_excel_to_json should be used instead.

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