autotask_delete_ticket_charge

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

The description builds on annotations by explicitly stating the action is 'DESTRUCTIVE — IRREVERSIBLE' and that it deletes 'all associated billing data', providing behavioral context beyond the destructiveHint annotation. It does not contradict 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 extremely concise, using only two sentences with a front-loaded warning. Every word is necessary and adds value.

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 two parameters and no output schema, the description covers the essential aspects: what is deleted, irreversibility, and need for confirmation. It could mention idempotency implications but is otherwise 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?

Input schema has 100% coverage with clear descriptions for both parameters (ticketId and chargeId). The description adds no additional meaning to the parameters beyond what the schema already provides.

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 deletes') and the resource ('ticket charge record and all associated billing data'). It is specific and distinct from other sibling delete tools (e.g., delete ticket checklist item) through the resource name.

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 includes the important guideline to confirm with the user before invoking due to irreversibility. However, it does not mention when to use this tool versus alternatives like autotask_update_ticket_charge for modifying charges instead of deleting them.

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