autotask_create_ticket_charge

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'create a charge' without mentioning side effects, authorization requirements, idempotency, or what happens on failure. The agent is left to infer basic write behavior.

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 long, immediately stating the action and purpose. Every word is informative, and the structure is front-loaded with the key verb and resource.

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 tool with 12 parameters and no output schema, the description covers the function and use case adequately. It lacks details about the return value (e.g., created charge ID) and error conditions, but these are somewhat implied for a create operation. The schema's parameter descriptions fill most gaps.

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 has 100% description coverage for all 12 parameters, so the schema already documents each field. The description adds marginal value by grouping charges as 'material, cost, or expense,' which helps contextualize the chargeType parameter. However, it does not explain any parameter beyond 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 'ticket charge,' with specific examples of charge types (material, cost, expense). It distinguishes itself from sibling tools like autotask_create_ticket_note or autotask_create_time_entry by focusing on non-labor billing.

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 provides clear context for when to use the tool: 'to bill clients for parts, travel, or other non-labor costs.' However, it does not explicitly exclude other scenarios or mention alternative tools for labor charges or discounts.

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