create_timeline

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

With no annotations, the description carries the full behavioral burden and covers little: it does not say whether the new timeline becomes the current timeline (a real question given the sibling set_current_timeline), what happens to existing timelines, what the call returns, or whether the timeline persists until saved.

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?

One short, front-loaded sentence with no wasted words. Brevity here reflects under-specification rather than tight craft, but structurally it is clean.

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?

For a creation tool with no annotations, no output schema, and an undocumented parameter, the description omits essentials: the creation's side effects, whether it becomes active, and how to reference the new timeline afterwards. Materially incomplete for an agent deciding how to call it.

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% and the single 'name' parameter is never mentioned in the description, so the agent gets no signal that it is optional or what happens if it is omitted (auto-generated name?). The description fails to compensate for the documentation gap.

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?

States a specific verb and resource ('Create an empty timeline') and scopes it to the current project, which separates it from get_timelines and create_bin. It does not explicitly name a sibling or clarify how it relates to create_project, but the action is unambiguous.

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 when-to-use guidance, no prerequisites stated, and no alternatives named. The phrase 'in the current project' hints that a project must be loaded first, but that is inference rather than instruction; nothing says when to prefer this over create_project or set_current_timeline.

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