autotask_delete_service_call_ticket_resource

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

The description adds concrete behavioral context beyond the annotations: '⚠ DESTRUCTIVE — IRREVERSIBLE. This action cannot be undone.' This aligns with the destructiveHint=true annotation and provides extra detail.

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, both essential. It uses a warning emoji for visibility and front-loads the destructive nature. No superfluous content.

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 delete operation with one parameter and no output schema, the description sufficiently explains behavior (irreversible, requires confirmation). The annotations further support the context.

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 any additional semantics for the parameter beyond what the schema already states ('The service call ticket resource 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 tool's action: 'Permanently removes a resource assignment from a service call ticket.' It uses a specific verb ('removes') and identifies the resource, distinguishing it from siblings like autotask_delete_service_call_ticket.

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 guideline: 'Confirm with the user before invoking.' However, it does not explicitly state when to use this tool vs alternatives (e.g., deleting the entire service call ticket instead of just a resource assignment).

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