autotask_delete_ticket_checklist_item

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

Annotations already set destructiveHint=true and readOnlyHint=false. The description adds emphasis on irreversibility and the need for user confirmation, providing context beyond annotations. It does not, however, mention authentication requirements or rate limits, but for a simple destructive action this is acceptable.

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 extremely concise: two sentences with no wasted words. The critical warning is front-loaded with a symbol, and every sentence adds value (warning, action, and usage instruction).

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 low complexity (2 required parameters, no output schema), the description is complete. It covers purpose, behavior, and usage guideline. The warning compensates for the lack of output schema. A minor gap is no mention of what happens on success/failure, but the tool is simple enough.

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 coverage is 100% (both parameters fully described in the schema). The description adds no additional meaning beyond what the schema already provides for parameters, so the baseline score of 3 is appropriate.

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: 'Permanently deletes a checklist item from a ticket.' It uses a specific verb ('deletes') and resource ('checklist item'), and distinguishes from sibling tools like search, create, or update checklist items.

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 a clear usage guideline: 'Confirm with the user before invoking.' This tells the agent when to use the tool (only after user confirmation). However, it does not explicitly exclude alternatives, but the destructive nature makes the context clear.

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