autotask_update_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 mentions 'Only fields provided will be changed,' which is useful partial-update behavior, but lacks critical information: whether this is a destructive mutation, what permissions are required, if there are rate limits, what happens on success/failure, or the response format. For a mutation tool with zero annotation coverage, this leaves significant gaps.

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 immediately states the core action and a key behavioral trait ('Only fields provided will be changed'). There's no wasted verbiage, and it's front-loaded with essential information.

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 mutation tool with 8 parameters, no annotations, and no output schema, the description is inadequate. It lacks behavioral context (e.g., side effects, error handling), usage guidance relative to siblings, and any information about return values. The partial-update hint is helpful but insufficient for the tool's complexity.

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 description coverage is 100%, so the schema fully documents all 8 parameters. The description adds no additional parameter semantics beyond implying partial updates apply to all fields. This meets the baseline of 3 where the schema does the heavy lifting, but the description doesn't enhance understanding of parameter interactions or constraints.

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 ('Update') and resource ('existing ticket charge'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'autotask_update_ticket' or 'autotask_create_ticket_charge', which would require mentioning it's specifically for modifying charges rather than tickets or creating new 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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing charge ID), compare to 'autotask_create_ticket_charge' for new charges, or indicate when partial updates are appropriate versus full replacements.

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