todoist_duplicates_merge

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

No annotations are provided, so the description carries full burden. It implies destructive behavior (deleting/completing tasks) but does not elaborate on side effects, reversibility, or permissions required. Barely adequate beyond what the action enum suggests.

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 sentences, action-oriented and front-loaded with the core functionality. No redundant information.

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 mutation tool with 3 well-documented parameters and no output schema, the description sufficiently covers the purpose and usage context. It lacks details on return values or confirmation, but the action is straightforward.

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 100%, baseline is 3. The description ties to parameters (keeping one, completing/deleting others) but adds no additional semantic detail beyond the schema's parameter descriptions.

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 'Merge duplicate tasks' with a specific verb and resource. It distinguishes from siblings by referencing 'todoist_duplicates_find', and specifies the action: keeping one task and completing or deleting the others.

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?

Explicitly says 'Use after todoist_duplicates_find to clean up duplicates,' providing clear contextual guidance on when to invoke this tool as part of a workflow.

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