autotask_delete_service_call_ticket_resource

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

With no annotations, the description must fully convey behavioral traits. It simply says 'Remove', implying deletion, but does not disclose whether the action is irreversible, what happens to related data, or any required permissions. The agent cannot infer safety or side effects from this minimal description.

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 concise sentence that efficiently communicates the tool's purpose without extraneous words. It is front-loaded with the key verb and resource.

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 tool with one parameter and no output schema, the description is moderately complete. It explains what is deleted and how to identify it. However, it lacks context about what the resource assignment represents and does not reference related tools (e.g., search_service_call_ticket_resources to find IDs).

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 has 100% description coverage for the single parameter. The description does not add any semantic value beyond the schema's own description ('The service call ticket resource record ID to delete'). Therefore, the baseline score 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: 'Remove a resource assignment from a service call ticket' and specifies the method 'by the resource record ID'. This distinguishes it from sibling delete tools that target other entities (e.g., delete_service_call_ticket, delete_quote_item).

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 is provided on when to use this tool versus alternatives like delete_service_call_ticket or search_service_call_ticket_resources. It does not mention prerequisites (e.g., the resource must be assigned), nor does it explain context such as when a resource assignment should be removed.

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