todoist_project_note_delete

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

No annotations are provided, so the description carries full burden. 'Delete' correctly implies a destructive action, but no additional details are given (e.g., irreversibility, permission requirements, side effects on related data). The description is accurate but lacks depth, resulting in a mid-range score.

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, six-word sentence with no filler or redundancy. It is as concise as possible while conveying core information. Every word serves a purpose, and the structure is appropriate for the tool's simplicity.

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 (one parameter, no output schema, no nested objects), the description covers the essential purpose. However, it lacks mention of typical behaviors like success output (e.g., returns nothing) or error handling. Despite these minor gaps, it is largely sufficient for a basic delete operation.

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 100% description coverage, with the single parameter 'note_id' described as 'The ID of the note to delete' in the schema. The tool description adds no additional meaning beyond the schema, hitting the baseline score of 3.

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 explicitly states the action ('Delete'), the resource ('project note'), and the identifier ('by ID'). Among sibling tools like todoist_comment_delete and todoist_project_delete, this clearly distinguishes itself. The verb-resource combination is specific and unambiguous.

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 like todoist_project_note_update or todoist_project_note_create. No context about prerequisites, such as needing an existing note ID, or when deletion is appropriate. The agent is left to infer usage from the name alone.

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