clear_habit_occurrence

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

With no annotations, the description must fully disclose behavior. It explains ID resolution but fails to specify the effect of 'clear' (e.g., unmark vs delete), side effects, or safety (destructive?). Leaves ambiguity about the tool's actual operation.

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?

Two concise sentences: first clearly states action and date format, second details ID flexibility. No fluff, front-loaded, every word earns 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?

While output schema exists (unmentioned), the description misses what the tool returns and any side effects. For a simple mutation tool, the behavioral gap (effect of clear) reduces completeness.

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 coverage is 0%, but the description richly explains 'habit_id' acceptance of multiple reference forms and resolution process, and gives date format. This adds significant value beyond the schema.

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 'Clear' and the resource 'habit occurrence' with a specific date format. However, it does not differentiate from sibling tools like 'mark_habit_occurrence' or 'reschedule_habit_occurrence', missing explicit scope boundaries.

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?

No guidance on when to use this tool vs alternatives. Context like prerequisites (occurrence must be marked) or when-not-to-use is absent, leaving the agent to infer from tool name alone.

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