mark_habit_occurrence

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions that habit_id is resolved to UUID and date defaults to today, but does not reveal idempotency, error handling, or whether it overwrites existing occurrences. Key behavioral traits are missing.

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, with a clear purpose in the first sentence and parameter details in a structured second paragraph. No superfluous text, though could be slightly more compact without losing meaning.

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?

The description covers habit_id and date well, but lacks information on error conditions, idempotency, or the relationship to clear_habit_occurrence. With an output schema present, return values are not required, but overall context for a complete agent decision is moderately adequate.

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 description adds significant meaning beyond the schema for habit_id (accepts various reference forms and resolves to UUID) and date (YYYY-MM-DD format, defaults to today). However, the 'done' parameter (boolean) is not explained, leaving a gap despite low schema coverage (0%).

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 'Mark a habit occurrence as done or not-done,' specifying the verb (mark), resource (habit occurrence), and the binary outcome. Among sibling tools like clear_habit_occurrence and reschedule_habit_occurrence, this tool is unambiguously distinct.

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 for marking a habit occurrence, but does not explicitly state when to use this tool versus alternatives like clear_habit_occurrence or other habit-related tools. No guidance on prerequisites or context.

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