Delete Habit

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

The description explicitly states 'This cannot be undone,' which is the most critical behavioral trait for a delete operation. Since no annotations are provided, the description carries the full burden and adequately discloses irreversibility. It doesn't mention permissions or cascading effects, but the primary hazard is covered.

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 two short sentences with zero waste. It front-loads the action and parameter, then adds the key warning. 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?

For a tool with one parameter, no output schema, and no nested objects, the description is fully sufficient. It covers the operation, the parameter, and the irreversible consequence. There is no ambiguity that would prevent correct invocation.

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 input schema already describes habit_id as 'Habit ID to delete' with 100% coverage. The description's phrase 'by its ID' simply repeats the schema. No additional meaning is added, so baseline 3 is appropriate.

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?

Description clearly states 'Delete a habit by its ID' – a specific verb and resource, and explicitly mentions the identifying parameter. This distinguishes it from sibling delete operations like delete_project and delete_task by naming 'habit' as the target.

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 use case is implied: use when you need to delete a habit. However, there is no explicit guidance on when not to use it, prerequisites, or how it differs from other delete tools. Among many delete siblings, no alternatives or exclusion criteria are given.

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