autotask_delete_service_call_ticket_resource

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

Annotations already declare destructiveHint: true. The description adds value by emphasizing the irreversible nature with '⚠ DESTRUCTIVE — IRREVERSIBLE. This action cannot be undone,' and provides a user confirmation requirement. This goes beyond the annotation to convey behavioral context and safety precautions. No contradiction with annotations.

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 sentences that effectively convey the destructive nature, irreversibility, and need for user confirmation. No unnecessary words, well-structured for quick understanding.

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 tool's simplicity (one required parameter, no output schema, annotations present), the description fully covers the necessary context: what it does, its destructive and irreversible nature, and a procedural instruction (confirm with user). It is complete for an agent to understand and use correctly.

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%, and the input schema already describes 'serviceCallTicketResourceId' as 'The service call ticket resource record ID to delete.' The description does not add additional meaning or context for this parameter, so it meets the baseline expectation without exceeding it.

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 and resource, distinguishing it from sibling tools like 'autotask_create_service_call_ticket_resource' (create) and 'autotask_delete_service_call_ticket' (delete ticket, not resource).

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 the instruction 'Confirm with the user before invoking,' which implies a usage guideline for safety. However, it does not explicitly state when to use this tool versus alternatives, such as when to delete a resource assignment as opposed to deleting the entire service call ticket. The sibling list shows related delete tools, but no comparative guidance is given.

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