resolve_duplicate_timeline

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

The description adds that the source timeline is preserved, which aligns with the non-destructive annotation. However, it does not cover other behavioral aspects like required permissions or state changes. The annotations already indicate non-readonly and non-destructive, so the description adds moderate value.

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, front-loaded sentence with no redundant information. Every word is necessary and contributes to understanding.

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 5 parameters, no schema description coverage, and an output schema, the description is too sparse. It does not explain return values, parameter interactions, or edge cases, leaving significant gaps for proper tool invocation.

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 description only hints at a version-named revision (new_name) but does not explain the other four parameters like timeline_id, make_current, etc. This leaves the agent with minimal guidance on how to populate them.

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 verb 'create' and the resource 'saved, version-named timeline revision' while specifying that the source is preserved. It distinguishes this tool from siblings like resolve_create_timeline, which creates a new timeline without duplication.

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 is provided on when to use this tool vs alternatives (e.g., resolve_create_timeline). It does not mention prerequisites, context, or what to avoid.

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