autotask_delete_service_call_ticket

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

Annotations already declare destructiveHint=true, but the description adds context: 'IRREVERSIBLE', 'cannot be undone', and a warning symbol. This elaboration is valuable beyond the annotations, though no additional behavioral details (e.g., cascading effects) are provided.

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 two sentences plus a warning symbol, extremely concise. It front-loads 'DESTRUCTIVE' and each sentence adds distinct value: irreversible action, what it does, and user confirmation requirement.

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 simple tool (1 parameter, full schema coverage, annotations present), the description adequately explains the action and its irreversibility. However, it could mention prerequisites or that it only removes the association, not the ticket or service call themselves.

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%, so baseline is 3. The description does not add extra meaning to the sole parameter serviceCallTicketId beyond what the schema already provides ('The service call ticket record ID to delete').

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 removes a ticket association from a service call') and explicitly marks it as destructive and irreversible. This differentiates it from siblings like autotask_create_service_call_ticket and autotask_search_service_call_tickets.

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 instructs to confirm with the user before invoking, which is critical usage guidance. However, it does not explicitly state when to use vs. alternatives, though the destructive nature and contrast with create/search are implied.

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