autotask_delete_ticket_charge

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

Annotations already indicate destructiveHint: true. The description adds that the action is irreversible and deletes 'all associated billing data,' providing context beyond the annotation. It does not contradict any annotation.

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 two concise sentences: a clear warning followed by the action statement. It is front-loaded with the ⚠ symbol and keywords, making it efficient and easy to parse.

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?

Given that the tool performs a straightforward deletion with no output schema, the description adequately covers the necessary context. It could mention success or failure responses, but it remains sufficient for an agent to understand the impact.

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 covers both parameters with descriptions (ticketId: 'The parent ticket ID', chargeId: 'The charge ID to delete'), achieving 100% coverage. The description does not add extra meaning to these parameters, so 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 tool's action: 'Permanently deletes a ticket charge record and all associated billing data.' It distinguishes itself from sibling tools like 'autotask_create_ticket_charge' and 'autotask_update_ticket_charge' by focusing on deletion.

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 instructs 'Confirm with the user before invoking,' providing a clear usage guideline for a destructive operation. It does not explicitly list exclusions but implies it should only be used when deletion is intended and irreversible.

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