task_delete

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

The word 'Permanently' is a meaningful behavioral disclosure indicating irreversibility, which is important for a delete operation. However, with no annotations at all, the description does not cover other relevant behavioral aspects such as permissions, cascading effects, or error behavior.

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, clear sentence. It front-loads the destructive nature ('Permanently') and the required identifier, with no unnecessary words.

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 single-parameter delete tool, the description covers the essential action and input. It does not delve into edge cases like deleting non-existent tasks or authorization, but the low complexity makes the description largely complete.

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 parameter taskId is already fully documented in the schema with a description and 100% coverage. The tool description adds no extra parameter-level meaning beyond what the schema already provides.

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 a specific verb ('delete'), a clear resource ('Figranium task'), and the identifier used. It unambiguously differentiates this tool from siblings like create_task, task_update, task_list, and task_execute.

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?

There is no guidance about when to use this tool versus alternatives, no prerequisites, and no indication of when deletion might be inappropriate. The description simply states the action without clarifying context or exclusions.

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