ticktick_checkin_habit

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

Annotations indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false, covering basic safety and idempotency. The description adds context with 'Requires v2 API authentication,' which is useful for auth needs not covered by annotations. However, it doesn't disclose additional behavioral traits like rate limits, error handling, or what happens on duplicate check-ins, missing opportunities to enhance transparency beyond the 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 highly concise with three short sentences: 'Record a habit check-in.' states the purpose, 'Track your daily progress toward habit goals.' adds context, and 'Requires v2 API authentication.' provides a prerequisite. Each sentence earns its place without redundancy, and the structure is front-loaded with the core action, making it efficient and easy to parse.

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 annotations covering read/write and idempotency, an output schema exists (though not detailed here), and parameters are minimal (3 with 0% coverage), the description is somewhat complete but lacks depth. It covers purpose and auth needs but misses parameter explanations and behavioral details like return values or error cases. For a mutation tool with low schema coverage, it should do more to compensate, resulting in an average score.

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%, meaning parameters (habit_id, value, date) are undocumented in the schema. The description doesn't add any parameter-specific information beyond the tool's general purpose, failing to compensate for the low coverage. Since there are 3 parameters, the baseline is lower than if coverage were high, but the description provides no details on what habit_id refers to or how value and date are used, resulting in a minimal score.

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 tool's purpose with 'Record a habit check-in' and 'Track your daily progress toward habit goals,' which specifies the verb (record/check-in) and resource (habit). It distinguishes from siblings like ticktick_get_habit or ticktick_update_habit by focusing on progress tracking rather than retrieval or modification. However, it doesn't explicitly contrast with ticktick_get_today_habits or ticktick_get_habit_stats, which might be related for viewing habits.

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 implies usage by stating 'Track your daily progress toward habit goals,' suggesting it's for logging habit completion, and 'Requires v2 API authentication' provides a prerequisite. However, it doesn't explicitly say when to use this tool versus alternatives like ticktick_update_habit for modifying habits or ticktick_get_today_habits for viewing today's habits, leaving some ambiguity in sibling differentiation.

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