autotask_create_ticket_charge

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

No annotations are provided, so the description must fully disclose behavioral traits. It only mentions creating a charge for billing, but lacks details on authorization, rate limits, side effects (e.g., ticket total updates), or reversibility. The description does not compensate for the lack of 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 concise with two sentences, each contributing value. It front-loads the core action and then provides usage context. No unnecessary words or redundancy.

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 has 12 parameters, no output schema, and a financial nature, the description is insufficient. It does not explain return values (e.g., created charge ID), how charges affect billing, or the need for external lookups (though schema covers chargeType). More context would be helpful for completeness.

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 all 12 parameters with descriptions (100% coverage), so the baseline is 3. The description adds no additional meaning beyond the schema; it only broadly mentions charge types. No extra value is provided for parameters beyond what is already in 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 verb 'Create' and the resource 'charge on a ticket', and specifies the types of charges (material, cost, expense). It distinguishes this tool from other create tools like autotask_create_ticket_note or autotask_create_ticket_attachment by mentioning billing for parts, travel, or non-labor costs.

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 when to use this tool (to add a billable charge to a ticket) but does not explicitly provide guidance on when not to use it or distinguish it from alternatives like autotask_create_time_entry for labor. No explicit context or exclusion criteria are given.

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