ticktick_delete_focus_record

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

The description adds significant behavioral context beyond what annotations provide. Annotations show destructiveHint=true and idempotentHint=true, but the description explicitly warns 'This cannot be undone' (enhancing the destructive nature) and specifies 'Requires v2 API authentication' (adding permission/version context not in annotations).

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 perfectly concise with three short, front-loaded sentences that each add value: the core action, a critical warning, and an authentication requirement. There's zero wasted text.

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 destructive operation with good annotations and an output schema (which handles return values), the description covers the essential behavioral warnings and authentication needs. The main gap is lack of usage guidance relative to sibling tools, but otherwise it's reasonably complete.

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?

With 0% schema description coverage (the schema only has generic 'Input for deleting a focus record'), the description provides no parameter information at all. However, there's only one parameter (record_id), so the baseline is 4, but the description doesn't compensate for the schema gap, so it scores 3.

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 'Delete' and the resource 'focus record', making the purpose immediately understandable. However, it doesn't differentiate this from sibling deletion tools like delete_folder, delete_habit, delete_project, delete_tag, or delete_task, which all follow the same pattern.

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 provides no guidance on when to use this tool versus alternatives. While it mentions authentication requirements, it doesn't explain when deletion is appropriate versus archiving or other operations, nor does it reference sibling tools for comparison.

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