autotask_delete_service_call_ticket_resource

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

Annotations already provide destructiveHint: true and readOnlyHint: false. The description adds extra behavioral context by explicitly stating 'IRREVERSIBLE' and instructing to confirm with the user. This goes beyond the annotations, but it could also mention potential side effects (e.g., cascade effects) or required permissions.

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: two sentences that include a warning symbol and clear, direct language. Every sentence adds value (purpose, irreversibility, instruction to confirm). No unnecessary 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 destructive single-parameter tool with strong annotations and no output schema, the description is complete. It covers what the tool does, the irreversibility, and provides user action guidance. No additional context is needed.

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%; the single parameter 'serviceCallTicketResourceId' has a clear description in the schema. The tool description does not add any additional parameter semantics beyond what the schema provides, so 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: 'Permanently removes a resource assignment from a service call ticket.' The verb 'removes' and the specific resource 'resource assignment' make the purpose unambiguous. It also effectively distinguishes from sibling delete tools that operate on different entities (e.g., service call tickets themselves).

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 warns about the destructive and irreversible nature, and instructs to confirm with the user. However, it does not explicitly specify when to use this tool versus alternatives (e.g., when to use other delete tools like autotask_delete_service_call_ticket). The context implies usage when removing a resource assignment, but lacks direct comparison.

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