Remove Todo Item

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds that deletion is permanent and provides a Claude Desktop timeout workaround, but does not cover auth requirements or broader failure modes.

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 core purpose, permanence warning, alternative routing, and example are front-loaded and efficient. The final paragraph about Claude Desktop timeout behavior is niche and lengthy, but it is clearly separated and potentially useful for that client.

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 annotations, full schema coverage, and an output schema, the description provides everything needed to select and invoke the tool correctly. It explains the effect, the alternative, and an example, while return values are handled by the output schema.

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 100%, so both entity_id and item are already documented. The description adds an example call, but the schema itself explains that item may be a UID or exact summary, so the description does not add substantial meaning beyond the structured data.

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 states a specific verb and resource: 'Remove an item from a Home Assistant todo list,' and clarifies it permanently deletes from the specified list. It distinguishes itself from ha_set_todo_item() by naming the alternative explicitly.

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?

It directly tells the agent when to use this tool versus the sibling alternative: to mark an item completed, use ha_set_todo_item() with status="completed". This is an explicit when/when-not guideline for the primary alternative.

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