autotask_create_ticket_charge

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

No annotations are provided, so description alone must convey behavior. It discloses that this tool is for creating billable charges but does not mention side effects, required permissions, or whether it modifies existing entities. The description is adequate but lacks depth.

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?

Two sentences, concise and front-loaded. First sentence states the action and resource, second sentence explains usage context. No unnecessary words.

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?

The tool has 12 parameters with full schema coverage. The description provides a high-level purpose but does not explain optionality like productID or status behavior. No output schema exists, so description could hint at return value but doesn't. Adequate but not comprehensive.

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 coverage is 100% for parameters, but the description does not add additional meaning beyond schema descriptions. However, it briefly categorizes charge types as material/cost/expense, which helps. Baseline is 3 due to high coverage, but the description adds slight context.

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 it creates charges on tickets for billing non-labor costs like parts and travel. It specifies the resource (ticket charge) and action (create), distinguishing it from sibling tools like autotask_create_ticket (creates tickets) and autotask_delete_ticket_charge (deletes charges).

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 mentions charges are for non-labor costs, implying when to use, but does not explicitly state when not to use or compare with alternatives like time entries (autotask_create_time_entry). However, the context of billing parts/travel provides some implicit guidance.

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