timeline_duplicate

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

With no annotations, the description must convey behavior. It fails to disclose side effects (e.g., whether the original timeline is modified), permissions required, or return behavior (e.g., creates new timeline but doesn't switch context).

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?

Single sentence is concise but under-specified. For a tool with two parameters and many siblings, it should include more context. Front-loading is fine, but content is too minimal.

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 number of sibling tools and lack of output schema, the description is critically incomplete. An agent cannot reliably determine usage, required inputs, or outcomes from this definition alone.

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?

No description of parameters beyond their names. The schema has 0% description coverage, and the description adds no meaning to 'new_name' or 'name_or_handle'. The agent must infer purpose from names alone.

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 'Duplicate a timeline' clearly identifies the verb and resource, but lacks specificity on what 'duplicate' entails (e.g., creates a copy of an existing timeline, keeps original unchanged). It does not differentiate from sibling tools like timeline_create or timeline_import.

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 such as timeline_create, timeline_import, or timeline_rename. No prerequisites or context about required state (e.g., current timeline) are mentioned.

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