Delete task

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

No annotations are provided, so the description carries the full behavioral burden and it delivers almost nothing. It does not say whether deletion is permanent or recoverable, what permissions are required, whether child records cascade, or what happens if the task_id does not exist.

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 single short sentence is front-loaded and free of padding, which is structurally fine. But the brevity reflects under-specification rather than disciplined conciseness, so it earns only a middling score.

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 destructive, irreversible-looking operation with no annotations and no output schema, the definition omits the details an agent needs: reversibility, required permissions, error behavior, and relationship to delete_request_task. The schema alone cannot cover these gaps.

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 single parameter task_id has 0% schema description coverage, and the description adds no meaning beyond the schema's own type constraints (positive integer or numeric string). The agent gets no hint about where a valid task id comes from or expected format.

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 concrete verb and resource ('Delete a task'), so the agent knows the operation is a destructive removal of a task. However, it does no work to distinguish this tool from siblings such as delete_request_task, and it essentially restates the tool name/title rather than adding definition.

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 on when to use this tool versus the related delete_request_task, or when a task should be updated/closed instead of deleted. No preconditions or exclusions are stated, leaving usage entirely to inference.

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