autotask_delete_service_call_ticket_resource

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

The description reinforces the destructive nature already indicated by annotations, adding the key detail that the action cannot be undone. This goes beyond the annotations' destructiveHint by specifying irreversibility and the need for user confirmation.

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: a two-sentence warning followed by the action statement. Every word adds value, and the warning is front-loaded for immediate agent awareness.

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 simple delete operation with one parameter and annotations covering destructiveness, the description fully covers what the agent needs: purpose, irreversibility, the need for confirmation, and the parameter reference. No 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 is fully described in the schema with a clear description. The tool description adds no additional parameter-level detail. With 100% schema coverage, baseline 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 (removes), the target (resource assignment from a service call ticket), and it distinguishes from sibling delete tools like autotask_delete_service_call or autotask_delete_ticket_charge by specifying the exact resource type.

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 includes a prominent warning 'DESTRUCTIVE — IRREVERSIBLE' and explicitly says 'Confirm with the user before invoking.' This provides clear when-to-use guidance, though it does not mention alternative non-destructive tools explicitly.

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