Delete a specific charge from a ticket in Autotask PSA by providing the parent ticket ID and charge ID.
Delete a ticket charge by ID. Requires both the parent ticket ID and charge ID.
| Name | Required | Description | Default |
|---|---|---|---|
| ticketId | Yes | The parent ticket ID | |
| chargeId | Yes | The charge ID to delete |
Changes observed during successful MCP inspections.
v2.18.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the burden. It indicates a destructive action but does not disclose potential side effects, authorization requirements, or irreversibility. The lack of annotations makes this a gap.
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, clear sentence without any unnecessary words, efficiently conveying the essential information.
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 deletion tool with no output schema, the description covers the required parameters and basic action. However, it could mention the success response or confirmation behavior to be fully 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?
Schema already describes both parameters with 100% coverage. The description adds that both are required and for the parent charge, but offers little extra meaning beyond the schema.
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 (delete), the resource (ticket charge), and the requirement for both ticket ID and charge ID, distinguishing it from other ticket-related operations like create or update.
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?
It specifies the need for both IDs, giving a prerequisite, but does not provide guidance on when to use delete instead of update or other alternatives, nor does it mention how to obtain the IDs.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.