timeline_lift

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

With no annotations provided, the description must carry the behavioral burden. It explicitly discloses that deletion is destructive ('Effects on those items are lost'), which is valuable, but it does not explain the meaning of the 'ripple' parameter, track scoping, or whether the operation is reversible. This is partial transparency, not full.

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 short sentences carry all the essential information with no filler. The destructive nature and selection methods are front-loaded, and every sentence earns its place.

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?

Although an output schema exists, the operational context is incomplete for a destructive tool with six optional parameters and no required fields. The agent is not told which parameter combinations are valid, what happens if no selection parameters are provided, how ripple affects deletion, or how track_type/track_index confine the deletion.

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?

The description adds meaning beyond the bare schema by explaining the two selection modes: 'by unique_id' maps to unique_ids, and 'by range' maps to start/end. However, it leaves track_type, track_index, and ripple unexplained, and schema description coverage is 0%, so these gaps are significant.

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 states a specific verb ('Delete'), a specific resource ('timeline items'), and the two selection mechanisms ('by unique_id or by range'). It clearly distinguishes this destructive operation from sibling tools like timeline_place and timeline_assemble, which are constructive/write operations.

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 this tool is for deletion of timeline items, but it gives no explicit guidance about when to prefer it over alternatives, when not to use it, or any prerequisites. It does not name sibling tools or exclusion conditions, so the usage context is only implied.

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