autotask_delete_service_call_ticket_resource

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

The description explicitly adds 'DESTRUCTIVE — IRREVERSIBLE' and 'This action cannot be undone,' going beyond annotations that only set destructiveHint=true. It also advises 'Confirm with the user before invoking.' This provides valuable behavioral context, though it could mention potential side effects (e.g., no cascade on the resource).

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 three sentences with a strong warning label, front-loading critical information. Every sentence adds value: purpose, irreversibility, and user confirmation.

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 no output schema, the description adequately covers purpose, destructiveness, and user confirmation. It could briefly clarify that it only affects the resource assignment, not the ticket or resource itself.

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 'serviceCallTicketResourceId' is fully described in the schema ('The service call ticket resource record ID to delete'), achieving 100% coverage. The description does not add further semantic detail, warranting the baseline score.

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 'Permanently removes a resource assignment from a service call ticket,' specifying the verb (removes), resource (resource assignment), and object (service call ticket). It distinguishes from sibling tools like autotask_delete_service_call_ticket, which deletes the ticket itself, by emphasizing 'resource assignment'.

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?

No guidance on when to use this tool versus alternatives such as autotask_delete_service_call_ticket (deleting the entire ticket) or autotask_delete_service_call (deleting the whole service call). The description only includes a warning, not context for tool selection.

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