export_timeline

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

The description lacks behavioral details: no mention of file creation, overwrite behavior, required permissions, side effects, or error conditions. Without annotations, the description carries full burden and falls short.

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 concise sentences with no extraneous text. The key point is front-loaded, but the second sentence could be integrated with the first. However, it earns its place by providing examples.

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?

With no output schema, no annotations, and 3 parameters, the description should explain the return value, error handling, and parameter constraints. It only covers export_type examples, leaving significant gaps.

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?

Only export_type is given examples (constant names like EXPORT_EDL). file_path and timeline_name have no description beyond the schema, which itself has 0% coverage (no parameter descriptions). The examples help but are incomplete.

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') and the resource ('a timeline') with a specific verb and direct object. Among sibling tools, it is distinct from import, create, delete, and render tools, so no ambiguity.

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 guidance on when to use this tool versus alternatives like import_timeline, render_to_file, or create_timeline. The description does not mention prerequisites, context, or exclusion criteria.

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