export_csv

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

With no annotations, the description carries full burden for behavioral disclosure. It fails to mention side effects (e.g., file overwrite), permissions needed, data volume limits, or the structure of the CSV output. The tool's safety profile (read vs write) is ambiguous.

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, which is concise, but it lacks structure and is overly terse. While no waste exists, the brevity sacrifices necessary detail, making it borderline underspecified.

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 has two parameters (one required), no output schema, and no annotations, the description is grossly incomplete. It does not explain what 'timeline data' encompasses, how the CSV is formatted, or what the 'include' parameter controls. The tool's behavior cannot be safely invoked based on this description alone.

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%, yet the description does not explain either parameter. 'filepath' and 'include' are not defined in context, leaving the agent to guess their meaning and valid values. The description adds no semantic value beyond the schema's type definitions.

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 'Export timeline data' and the output format 'CSV', which is a specific verb-resource combination. It distinguishes from sibling export tools that target other formats like EDL or XML.

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?

No usage guidance is provided. The description does not mention when to use CSV vs other export formats, nor prerequisites like timeline state or file system requirements. Among many sibling export tools, no differentiation criteria are given.

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