duplicate_timeline

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

Without annotations, description should disclose behavior. It only says 'Duplicate', implying creation of a copy, but does not clarify if the original remains intact, or any side effects. Minimal transparency.

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 sentence, direct and no waste. Efficient, though could be slightly more structured with additional context.

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?

No output schema, and parameters are not fully explained. The description does not cover what happens on success/failure, or what the output is. Incomplete for a tool that modifies state.

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 has 0% description coverage, so description must explain parameters. It only hints at 'new_name' but does not explain 'name' (the source timeline). The meaning is not fully clarified.

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?

Description clearly states the action 'Duplicate' and resource 'a timeline', and mentions the new name. It is specific about what the tool does, but does not differentiate from sibling timeline tools beyond the verb.

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 create_timeline or import_timeline. No prerequisites or notes about existing timelines are provided.

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