autotask_delete_service_call_ticket_resource

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

Annotations already mark destructiveHint=true. The description reinforces this with 'DESTRUCTIVE — IRREVERSIBLE' and adds context about user confirmation and permanence, which is valuable beyond the 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 two sentences with an attention-grabbing warning emoji. It is front-loaded with the destructive nature and provides clear, concise guidance without any extraneous words.

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 one-parameter deletion tool with no output schema, the description covers the essential aspects: what it does, that it is irreversible, and to confirm with user. It could mention the outcome (e.g., success or failure) but overall is sufficiently complete.

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 already describes the single parameter 'serviceCallTicketResourceId' as 'The service call ticket resource record ID to delete'. With 100% schema coverage, the description adds no further semantic detail about the parameter, so the baseline 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 action: 'removes a resource assignment from a service call ticket'. It uses a specific verb and resource, and is distinguishable from sibling tools like autotask_delete_service_call_ticket (which deletes the entire ticket) and autotask_create_service_call_ticket_resource (which creates assignments).

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 explicitly advises to 'Confirm with the user before invoking' and emphasizes irreversibility. However, it does not explicitly contrast with the alternative sibling tool for deleting the whole ticket, which would further clarify when to use this tool instead.

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