autotask_create_ticket_charge

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Create charge' but does not reveal if the operation requires permissions, what side effects occur, error handling for missing tickets, or how the ticket is modified. The agent gets no insight into behavior beyond mutation.

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 a single, efficient sentence that front-loads the core purpose. It is appropriately sized but could be slightly more structured without losing conciseness.

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?

With 12 parameters, no output schema, and no annotations, the description is minimal and incomplete. It does not explain what a 'charge' means in Autotask, the expected return value, or how to handle optional vs required fields effectively. An agent would need external knowledge to use this tool correctly.

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%, so baseline is 3. The description adds no parameter semantics beyond the schema's own descriptions, such as explaining what chargeType is or how unitQuantity relates to billing. No additional value provided.

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 explicitly states 'Create charge on ticket for materials, costs, or expenses.' This is a specific verb (create) and resource (charge on ticket), clearly differentiating it from sibling tools like autotask_delete_ticket_charge and autotask_update_ticket_charge, and other create tools in the Autotask suite.

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 no guidance on when to use this tool versus alternatives, such as update or delete charge tools. There is no mention of prerequisites, contexts where charges apply, or when not to use it.

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