export_to_csv

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

No annotations provided, so the description carries full burden. It explains the tool reads records and returns CSV, details multivalue expansion behavior, and implies it is read-only. No destructive actions mentioned, which is appropriate for an export.

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 with a concise purpose statement, usage hint, then formatted Args and Returns sections. Every sentence adds value and is front-loaded.

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 complexity (4 parameters, output schema exists), the description fully covers the behavior, including multivalue handling and return format. It explains output fields despite having an output schema.

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 includes an explicit Args section that thoroughly explains each of the four parameters: file_name, record_ids, expand_mv, and mv_delimiter, including defaults and behavior.

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 records from a Universe file to CSV format, specifying the verb 'Export', the resource 'records from a Universe file', and the output format CSV. It distinguishes from sibling tools like export_to_json.

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 a usage hint: 'Useful for spreadsheet import and data analysis.' This gives context but does not explicitly state when not to use or compare with alternatives like export_to_json.

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