Create Habit

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

No annotations are provided, so the description must disclose side effects and behavior. It only says 'Create a new habit' and lists fields, without mentioning permissions, return value, error conditions, or side effects. It also omits two parameters (step, section_id) from the description, reducing 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?

A single, front-loaded sentence with no fluff. It clearly communicates the action and key fields in ~20 words, earning its place.

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?

With 8 parameters, no output schema, and no annotations, the description is too sparse. It omits two parameters, does not state the required field (name), and provides no information about the return value or side effects. The schema covers parameter definitions, but the description fails to give operational context.

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?

The schema has 100% parameter description coverage, so the baseline is 3. The description adds no new meaning beyond the schema; it merely repeats a subset of field names without additional detail. It does not explain the omitted step and section_id parameters.

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 action and resource: 'Create a new habit.' It lists the key fields, distinguishing it from other create tools like create_task or create_project. The name and title reinforce the purpose.

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 context is clear: use this tool when you want to create a habit. It does not explicitly mention alternatives or exclusions, but the tool name and sibling context (e.g., ticktick_get_habits, ticktick_delete_habit) make the intended usage obvious.

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