autotask_delete_service_call_ticket

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

The description adds value beyond annotations by explicitly stating 'IRREVERSIBLE' and 'Cannot be undone', and by instructing user confirmation. The annotations already indicate destructiveHint: true, but the description reinforces the irreversible nature and adds safety guidance.

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, consisting of two short sentences. It front-loads the warning and states the purpose and precaution without any unnecessary words. Every sentence earns its place.

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 single-parameter delete tool with no output schema and annotations providing destructive info, the description covers the essential aspects: what it does, irreversible nature, and user confirmation. It is complete enough for an agent to understand the tool's behavior and necessary precautions.

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 input schema covers 100% of parameters with a description for serviceCallTicketId. The tool description does not add any additional parameter information beyond what the schema provides, 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 tool 'permanently removes a ticket association from a service call', specifying the verb 'removes' and the resource 'ticket association from a service call'. It distinguishes from sibling tools like autotask_create_service_call_ticket (create) and autotask_delete_service_call (delete entire service call).

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 'Confirm with the user before invoking', providing a usage caution. However, it does not explicitly state when to use this tool versus alternatives (e.g., updating instead of deleting) nor when not to use it. The guidance is minimal and lacks comparison to other tools.

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