create_export

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

With no annotations, the description carries the full burden. It clearly states the core behavior (creating a new export) and the input scope. However, it does not disclose potential side effects, whether the operation is asynchronous, permission requirements, or the fact that 'source' can be 'preview' rather than only recorded footage.

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 two sentences, front-loaded with the primary action, and contains no filler. Every word contributes to understanding the tool's purpose.

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?

The tool has six parameters and no annotations, but an output schema exists. The description covers the main purpose and required parameters, yet it omits context around optional parameters like source and playback, and does not explain how the export process behaves (e.g., whether it's immediate or queued). This is adequate but not fully complete.

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 coverage is 100% with descriptions for all six parameters. The description adds value by framing start/end as defining a section of recorded video and specifying the camera, but it does not explain the optional parameters (name, source, playback) beyond what the schema already provides.

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 uses a clear verb ('Create') and resource ('video export'), and specifies the scope: 'a section of recorded video between the start and end timestamps for the specified camera.' This distinguishes it from sibling tools like delete_export, rename_export, and get_export.

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 implies when to use this tool (when you need a video export from recorded footage) and provides clear context around timestamps and camera. However, it does not explicitly state when not to use it or mention alternatives such as preview source or other export-related tools.

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