autotask_delete_service_call_ticket

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

Annotations already provide destructiveHint=true and idempotentHint=false. The description adds context: 'this action cannot be undone' and reiterates the destructive nature. This aligns with annotations and adds value by emphasizing irreversibility, but does not disclose other behaviors like cascading effects or permission requirements.

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?

Two sentences with clear structure: warning symbol and label first, then irreversible action, then user confirmation instruction. No extraneous words. Front-loaded with critical safety information.

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 destructive tool with one parameter, the description fully covers what the agent needs: purpose, irreversibility, and need for user confirmation. No output schema is needed. Annotations cover the remaining safety profile.

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% with a single required parameter described as 'The service call ticket record ID to delete.' The description adds no further meaning beyond the schema, so baseline 3 applies.

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.' It uses a specific verb ('removes') and resource ('ticket association from a service call'), distinguishing it from sibling tools like autotask_delete_service_call or autotask_delete_ticket_checklist_item.

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' as a usage guideline. However, it does not provide explicit when-to-use or when-not-to-use guidance relative to alternatives (e.g., autotask_delete_service_call). The guidance is minimal but present.

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