autotask_delete_ticket_charge

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

With no annotations, the description must cover behavioral traits. It states the operation is a deletion, which implies irreversibility, but does not disclose if there are side effects (e.g., cascading deletes) or authorization requirements. The description is minimal but not misleading.

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 action, and no unnecessary words. It is concise and efficient.

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 simplicity of the tool (two required numeric parameters, no output schema), the description provides the essential purpose and inputs. However, it lacks optional details like error handling, response format, or permission hints, which would be helpful for an agent.

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%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions, which already specify 'The parent ticket ID' and 'The charge ID to delete'.

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 a ticket charge by ID') and specifies the required identifiers ('parent ticket ID and charge ID'). It distinguishes itself from sibling tools like autotask_create_ticket_charge (create) and autotask_update_ticket_charge (update) 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 implies that both ticketId and chargeId are needed, matching the 'required' schema. However, it does not provide guidance on when to use this tool versus alternatives (e.g., searching for charges first) or any prerequisites like permissions.

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