autotask_update_ticket_charge

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

Since no annotations are provided, the description carries full burden for behavioral disclosure. It clearly communicates partial update semantics ('Only fields provided will be changed'), which is crucial for a mutation tool. However, it does not disclose other behavioral aspects like required permissions, idempotency, or side effects, which would be beneficial.

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 extremely concise at two sentences and 16 words, front-loading the purpose. Every word is necessary; there is no redundancy. It achieves maximum information density without being verbose.

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 8 parameters and no output schema or annotations, the description is minimal. It covers the basics but lacks explanation of the return value, error conditions, or the concept of a ticket charge. For a tool with moderate complexity, more context (e.g., response behavior, prerequisite charge existence) would improve 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 already describes all 8 parameters with detailed descriptions, so the baseline is 3. The description adds value by explicitly stating that only provided fields will be changed, which clarifies that optional parameters indeed leave existing values untouched—a nuance not fully captured in the schema. This incremental update semantics are clearly communicated.

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 'Update an existing ticket charge' with a specific verb (update) and resource (ticket charge). It distinguishes itself from sibling tools like create, delete, and get, as those have different verbs. This leaves no ambiguity about the tool's core function.

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 implicit guidance by stating it updates existing tickets charges, implying it should be used when an existing charge needs modification. However, it does not explicitly contrast with alternatives like autotask_create_ticket_charge for new charges or autotask_delete_ticket_charge for removal, leaving the agent to infer usage boundaries.

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