autotask_delete_service_call_ticket_resource

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates this is a destructive operation ('Remove'), but doesn't specify whether this requires special permissions, if the deletion is permanent/reversible, what happens to related data, or any rate limits. For a deletion tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and includes all essential elements: verb, target, and mechanism. Every word earns its place in conveying the tool's purpose.

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 single-parameter deletion tool with no output schema and no annotations, the description adequately covers the basic purpose but lacks important context. It doesn't explain what happens after deletion (success/failure responses), potential side effects, or error conditions. The description is minimally viable but leaves gaps that could hinder effective tool invocation.

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 schema description coverage is 100%, with the single parameter 'serviceCallTicketResourceId' fully documented in the schema. The description adds minimal value beyond the schema by mentioning 'resource record ID' but doesn't provide additional context about format, validation, or where to obtain this ID. Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Remove a resource assignment'), target resource ('from a service call ticket'), and mechanism ('by the resource record ID'). It distinguishes itself from sibling tools like 'autotask_create_service_call_ticket_resource' and 'autotask_delete_service_call_ticket' by specifying it removes resource assignments rather than creating them or deleting entire tickets.

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 no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. While it's clear this is for removing resource assignments, it doesn't specify scenarios where this is appropriate versus other deletion tools or mention any dependencies like needing an existing assignment to delete.

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