delete_task

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the basic deletion action, omitting critical details such as whether the deletion is permanent or reversible, cascading effects (e.g., on subtasks), required permissions, or result format. The minimal description does not adequately inform the agent about side effects or constraints.

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 highly concise (one sentence, five words). However, it sacrifices important behavioral and usage details. While front-loaded and to the point, it does not earn its place fully because it omits information that would not significantly lengthen it. A sentence like 'Permanently removes a task and its associated subtasks' would add clarity without losing conciseness.

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 required parameter, no nested objects), the description should cover basics like return value (output schema exists but undocumented), permanence, and preconditions. The current description fails to provide this context, leaving the agent with insufficient information to use the tool safely and effectively.

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?

Schema description coverage is 0% (the description does not describe parameters). The only parameter, task_id, is hinted at by 'by ID' but lacks specifics such as format, length, or source. The description adds minimal value beyond the schema, failing to compensate for the lack of schema-level descriptions.

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 clearly states the action ('Delete') and the resource ('a task'), and specifies the identifier ('by ID'). It is concise and unambiguously distinguishes this tool from sibling tools that delete other entities or perform different operations on tasks.

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 updating the task status or archiving. It does not mention prerequisites (e.g., task existence, permissions) or caution against unintended deletions.

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