delete_todo_item

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

The description only says 'Delete' which is already implied by the tool name and the destructiveHint annotation. It adds no additional behavioral context such as irreversibility, permission requirements, or side effects.

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, front-loading the action in the first sentence and then listing the single argument with a brief explanation. No filler or redundancy.

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 delete operation with one parameter and an output schema, the description covers the essential purpose and argument. It omits any note about permanence or error behavior, but given the destructiveHint and output schema, these are not critical gaps.

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 explicitly explains 'todo_item_id: The numeric to-do item ID', providing semantic meaning beyond the raw schema type of integer. This compensates for the 0% schema description coverage.

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 to-do item' with a specific verb and resource, and the tool name reinforces this. It is unambiguous and distinct from sibling tools like update or complete.

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 provides no guidance on when to use this tool versus alternatives such as complete_todo_item or update_todo_item. It simply states the action without explaining prerequisites or exclusions.

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