delete_todo

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

With no annotations, the description fully discloses behavior: 'destructive, irreversible', 'first call deletes; subsequent calls error'. This clearly communicates that the tool is a mutation with side effects and specific error handling.

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 concise (three sentences plus example and side effects), front-loaded with the core action, and every sentence adds value: purpose, alternative, example, and behavioral notes.

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 tool's simplicity (1 parameter, no output schema, no annotations), the description fully covers its purpose, usage guidance, side effects, and error behavior, leaving no gaps for an AI agent.

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% (the id parameter is fully described as 'UUID of the todo to delete'). The description adds an example but does not significantly enhance meaning beyond the schema, so baseline score of 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?

The description clearly states that the tool permanently deletes a todo by ID, using a specific verb ('delete') and resource ('todo'). It distinguishes itself from the sibling tool 'mark_todo_done' by explicitly recommending that alternative for mere completion.

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 explicit when-to-use ('permanently delete'), when-not-to-use ('prefer mark_todo_done'), and details on error behavior ('subsequent calls with the same id error'). This gives the AI agent clear decision criteria.

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