export_csv

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

Discloses how formulas, dates, and empty cells are handled. Though annotations are absent, the description adds important behavioral traits. Could mention overwrite behavior and file creation, but overall informative.

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 with no filler. Front-loaded purpose, every sentence adds value. Efficiently explains key behaviors and alternatives.

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 6 parameters and no output schema, the description covers main behaviors but omits details on delimiter, overwrite, and file path. It includes helpful alternative guidance, but gaps remain for complete understanding.

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?

Parameter schema has 0% coverage, so description must compensate. It explains range/sheet usage implicitly but does not detail csv_path, delimiter, overwrite, or format. Adds some context but not comprehensive.

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 exports a range or sheet's used range to CSV, distinguishing it from siblings like export_json and export_pdf.

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?

Provides specific guidance on when to use alternatives (recalculate_workbook + read_calculated_range for computed values). Does not explicitly compare to export_json/export_pdf, but gives clear context for a common scenario.

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