taiga_tasks_delete

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the verb 'delete' without explaining consequences such as permanence, permission requirements, or cascading effects. It does not disclose what happens to associated attachments or comments, nor the response format.

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 concise sentence that efficiently communicates the tool's purpose without extraneous information. It is appropriately sized for a simple delete operation.

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?

Although the schema covers the parameter, the description provides no context about the operation's side effects, irreversibility, or required permissions. For a destructive delete action with no annotations or output schema, the description is incomplete and leaves the agent guessing about the outcome.

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 already documents the single required parameter 'id' as 'Task ID', giving 100% coverage. The description adds no additional information about parameter semantics, so the baseline score of 3 applies given the schema's clarity.

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 'Delete a task' clearly states the action (delete) and the target resource (task), distinguishing it from sibling tools like taiga_tasks_list, taiga_tasks_get, and taiga_tasks_update. It is specific and unambiguous despite being brief.

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. It does not mention prerequisites, irreversible nature, or that taiga_tasks_delete is the appropriate choice when permanently removing a task. No exclusions or context are given.

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