delete_habit

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

The description mentions 'permanently,' indicating irreversibility, and notes Auth V2. However, without annotations, it lacks details on side effects or constraints. More could be disclosed for a delete 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?

The description is extremely concise with no superfluous information. It front-loads the action and uses brackets for metadata, making it efficient.

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?

For a simple one-parameter delete tool, the description covers the essential: permanence, auth, related tools. No output schema needed, and context is complete.

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?

With 0% schema description coverage, the description provides a brief arg line for habit_id ('The habit ID to delete'), adding minimal meaning beyond the schema's type and name. It partially compensates but could be richer.

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 'Delete a habit permanently,' which is a specific verb and resource. It distinguishes from sibling tools like update_habit and list_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 lists related tools (list_habits, update_habit) and categorizes under Habits with Auth V2, but does not explicitly state when to use this tool versus alternatives or any prerequisites.

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