delete_todo

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'interactive prompts' which suggests some user interaction, but it doesn't clarify what this means operationally (e.g., confirmation dialogs, multi-step processes). It also fails to address critical aspects like whether deletion is permanent, requires specific permissions, or has 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 a single, efficient sentence that directly states the tool's purpose. It's front-loaded with the core action ('Delete a todo item') and adds a qualifying detail ('with interactive prompts'). There's no wasted verbiage or redundant information.

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 destructive operation like deletion with no annotations and no output schema, the description is insufficient. It doesn't explain what 'interactive prompts' entail, what happens after deletion (e.g., confirmation message, error handling), or how this tool relates to sibling tools like 'update_todo'. More context is needed for safe and effective use.

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 has 1 parameter with 100% coverage, so the schema fully documents the 'authToken' parameter. The description doesn't add any parameter-specific information beyond what the schema provides, which is acceptable given the high schema coverage. With only one parameter, the baseline is appropriately high.

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 the tool 'Delete a todo item' which provides a clear verb+resource combination, but it doesn't specify what distinguishes this from the sibling 'update_todo' tool (which might also modify or remove todos). The addition of 'with interactive prompts' adds some specificity but doesn't fully differentiate from alternatives.

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?

No explicit guidance is provided about when to use this tool versus alternatives like 'update_todo' or 'list_todos'. The description mentions 'interactive prompts' which might imply a specific context, but it doesn't state when this tool is appropriate or when other tools should be used instead.

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