create_habit

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

Since no annotations are provided, the description carries the full burden. It discloses that habits reset each period and unfinished occurrences do not carry forward, which is a key behavioral trait. It also provides examples for the recurrence field structure. It does not cover auth needs or potential side effects.

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 concise, using a brief summary and bullet points for optional fields. It front-loads the key difference from chores. The structure is clean, though the mention of v0.2 optional fields could be streamlined.

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 complexity of the tool (6 parameters, output schema present), the description lacks completeness. Only the recurrence parameter is explained in detail. The extra fields mentioned without schema presence and lack of explanation for other parameters leave gaps.

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%, so the description must add meaning. It provides examples and shapes for the recurrence parameter but does little for other parameters like title, description, complete_by, parent_id, labels. Additionally, it mentions optional fields (deadline_time_of_day, subtask_template) that are not in the input schema, which could confuse.

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 'Create a recurring habit that resets each period', providing a specific verb and resource. It distinguishes habits from chores by explaining that unfinished occurrences do not carry forward, which sets it apart from sibling tool create_chore.

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 explains when to use habits instead of chores by contrasting the reset behavior. However, it does not explicitly state 'use this when you want to create a habit' or provide exclusions for other siblings like create_task or create_event.

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