export_sheet_to_csv

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains that content can be returned inline or written to a file, and it fully documents the return dict fields. It does not discuss overwrite behavior or auth expectations, but for a simple export tool the behavioral contract is well covered.

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: a one-line purpose, a bullet list of parameters, and a bullet list of return fields. Each item adds necessary information and none is redundant or filler. It is longer than usual but earns its length given the zero schema coverage.

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 five parameters, no annotations, and no schema-level descriptions, this description covers everything an agent needs: required arguments, optional behavior, output path semantics, delimiter options, range handling, and return contract. Nothing critical is missing 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 description coverage is 0%, but the description meaningfully explains every parameter: file_path, sheet_name, output_path including the special 'return inline' value, delimiter with its allowed values and default, and cell_range with its default behavior. This fully compensates for the missing 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 opens with a specific verb and resource: 'Export a single Excel sheet to a CSV file.' It also says 'single', which distinguishes it from multi-sheet export tools, and the CSV target clearly differentiates it from siblings like export_sheet_to_text and export_sheet_to_markdown.

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 gives clear context for when to use the tool: whenever a single Excel sheet must be converted to CSV. It explains the inline return mode and optional range behavior, though it does not explicitly name alternative tools or state when not to use this tool. That prevents a 5 but the context is clear enough for selection.

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