Delete Todo

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

Annotations already indicate destructiveHint=true, and the description reinforces this with 'cannot be undone' and 'permanently removes.' It adds context that the tool affects 'Schedule (Legacy)' records, clarifying the entity. No new information on authorization or side effects beyond annotations.

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 verbose and repetitive, stating 'cannot be undone' twice and including unnecessary API details. It could be condensed to one or two sentences without losing meaning. The information is front-loaded but inefficiently presented.

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 tool with no output schema, the description covers purpose, deprecation, permanence, and required params. However, it lacks information about the response (e.g., empty body) and fails to reconcile the 'Todo' vs 'Schedule' naming, which could confuse agents.

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 coverage is 100%, so the description adds little value. It merely repeats that 'id' and 'project_id' are required, which is already in the schema. No additional semantic meaning or usage hints for the parameters.

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 verb 'Delete' and resource 'ToDo Item' are clear, but the description confusingly alternates between 'ToDo Item' and 'Schedule (Legacy) records,' making the exact resource ambiguous. It does distinguish from siblings by specifying scope (in a Project) but lacks differentiation from other delete tools.

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?

Explicitly states deprecation and provides an alternative endpoint. It also clarifies that the tool is for permanent deletion ('cannot be undone'). No guidance on when to use this over other delete tools, but the deprecation warning is a strong usage signal.

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