tasks_delete

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

With no annotations, the description carries the full burden. It clearly states the operation is permanent ('cannot be undone') and warns about cascading effects on subtasks. This provides good transparency about the destructive nature, though it omits details like required permissions or task state prerequisites.

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 well-structured with a clear opening sentence, a separate 'Workflow tips' section, and a 'Common use cases' section. It is concise and front-loaded with the main purpose. Minor redundancy ('Delete an existing task' and 'Permanently removes a task') could be merged.

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 simple tool (one required param, no output schema, no nested objects), the description covers the essential points: what it does, permanence, side effects on subtasks, and typical usage patterns. It does not describe the return value or authentication requirements, but for a delete operation, these are less critical.

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% coverage for the single 'id' parameter, so the baseline is 3. The description adds value beyond the schema by providing concrete usage examples (e.g., { 'id': 123 }) and workflow guidance to retrieve the ID via tasks/list, which helps the agent understand how to construct the call.

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 'Delete an existing task' and 'Permanently removes a task from the system,' with clear verb and resource. It distinguishes from sibling task tools (create, get, list, update) by specifying the delete action.

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?

Provides workflow tips including using tasks/list to find the ID, noting irreversibility, and potential impact on subtasks. It also gives common use cases with examples. However, it does not explicitly state when not to use or compare to alternatives, though no alternative delete exists for tasks.

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