autotask_delete_ticket_charge

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

No annotations are provided, so the description carries full burden. It discloses that deletion requires specific IDs, but lacks details on permissions, reversibility, side effects (e.g., impact on billing), or response behavior. For a destructive operation, this is a significant gap in behavioral context.

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 sentences, front-loaded with the core action, and has zero wasted words. Every sentence directly contributes to understanding the tool's purpose and requirements.

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 the tool is a destructive delete operation with no annotations and no output schema, the description is insufficient. It misses critical details like confirmation prompts, error handling, or what happens post-deletion, leaving gaps for safe agent invocation.

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 description coverage is 100%, with clear parameter descriptions in the schema. The description adds minimal value by reiterating that both IDs are required, but doesn't provide additional context like format examples or validation rules beyond what the schema already documents.

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') and resource ('ticket charge by ID'), making the purpose unambiguous. It distinguishes from sibling tools like 'autotask_create_ticket_charge' and 'autotask_update_ticket_charge' by specifying deletion, though it doesn't explicitly contrast with other delete operations (e.g., 'autotask_delete_service_call').

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 implies usage by stating 'Requires both the parent ticket ID and charge ID,' which suggests prerequisites but doesn't explicitly guide when to use this tool versus alternatives like updating or searching for charges. No explicit when-not-to-use or sibling alternatives are mentioned.

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