autotask_update_ticket_charge

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

No annotations are provided, so the description must carry full behavioral disclosure. It states 'Update' (mutation) and partial update behavior, but omits side effects, reversibility, error handling for invalid chargeId, or return format. For a mutation tool, this is insufficient.

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 with two short sentences that front-load the action and key behavior. Every word adds value with no redundancy.

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 8 parameters, no output schema, and no annotations, the description is too sparse. It does not explain return values, error scenarios, or constraints like permission requirements. For a complex mutation tool, more detail is needed.

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?

Input schema has 100% description coverage for all 8 parameters, so the schema already documents parameter meaning. The tool description adds no extra semantics beyond 'Only fields provided will be changed,' which is implicitly captured by the optional nature of non-required fields.

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 action ('Update'), the resource ('an existing ticket charge'), and the partial update behavior ('Only fields provided will be changed'). It effectively distinguishes from sibling tools like 'autotask_create_ticket_charge' and 'autotask_delete_ticket_charge'.

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 implies usage for partial updates but lacks explicit when-to-use or when-not-to-use guidance. It does not compare with alternatives like 'autotask_create_ticket_charge' or mention prerequisites such as ticket charge existence.

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