autotask_update_ticket_charge

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

No annotations were provided, so the description carries the burden. It states 'Only fields provided will be changed,' which implies a partial update behavior. However, it does not disclose whether this operation has any side effects, requires specific permissions, or is reversible. Lacks details on error handling or idempotency.

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 very concise at two sentences. It is front-loaded with the core action. Every word is useful, but it could expand slightly on usage context 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?

Given the complexity (8 parameters, no output schema), the description provides basic functional clarity but lacks completeness. It does not explain what happens on success (e.g., returns updated charge object?), nor does it address constraints like which fields are required or related to ticket context.

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 each parameter has a description. However, the tool description adds no extra explanation beyond the schema. For example, it does not clarify which fields are commonly updated together or any dependencies between parameters. Baseline of 3 is appropriate.

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 states the tool updates existing ticket charges and specifies that only provided fields change. It clearly identifies the target resource (ticket charge) and the action (update). However, it does not explicitly distinguish it from siblings like autotask_update_ticket, which might update different aspects of a ticket.

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?

No guidance on when to use this tool versus alternatives. For example, compared to autotask_create_ticket_charge or autotask_search_ticket_charges, there is no mention of when to update vs create or search. The description only states what it does, not when to invoke it.

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