Remove checklist items from Autotask tickets to maintain accurate task tracking and project management workflows.
Delete a checklist item from a ticket.
| Name | Required | Description | Default |
|---|---|---|---|
| ticketId | Yes | The parent ticket ID | |
| itemId | Yes | The checklist item ID to delete |
Changes observed during successful MCP inspections.
v2.18.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavioral traits. It only states it's a delete operation but lacks details on side effects, permissions, reverting, or any impacts beyond deletion. Minimal transparency.
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?
Single sentence, no wasted words, front-loaded with action. Appropriate length for a simple 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?
For a straightforward delete with no output schema, the description is minimally adequate. However, it lacks context about error handling, confirmation, or related operations, which could be useful given the many sibling tools.
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 covers both parameters (ticketId, itemId) with clear descriptions. Baseline score is 3 due to 100% schema coverage; the tool description adds no extra 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?
Description clearly states the action: 'Delete a checklist item from a ticket.' It uses a specific verb (delete) and resource (checklist item from a ticket), and is distinct from sibling tools that handle other entities or operations.
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?
No guidance on when to use this tool vs alternatives (e.g., update_ticket_checklist_item). No prerequisites, context, or exclusions mentioned. The description is too brief to help an agent decide when to invoke it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.