autotask_create_ticket_charge

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It states this is a creation tool but doesn't mention required permissions, whether it's idempotent, what happens on failure, or what the response contains (no output schema). The description adds some context about billing purposes but misses key operational traits for a mutation tool.

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?

Two sentences with zero waste. The first sentence states the core purpose, and the second provides usage context. Every word earns its place, and the most important information (what the tool does) is front-loaded.

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 12-parameter mutation tool with no annotations and no output schema, the description is incomplete. It explains the 'what' and 'why' but misses critical operational context: required permissions, error handling, response format, and system constraints. The schema covers parameters well, but behavioral transparency is inadequate for safe invocation.

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 already documents all 12 parameters thoroughly. The description adds minimal value beyond the schema by mentioning charge types and billing purposes, but doesn't provide additional syntax, format, or constraint details for any parameters. Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('Create a charge') and resource ('on a ticket'), with examples of charge types ('material, cost, or expense') and use cases ('bill clients for parts, travel, or other non-labor costs'). It distinguishes from siblings like autotask_create_ticket (creates tickets) and autotask_create_time_entry (creates labor 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 clear context for when to use this tool ('Used to bill clients for parts, travel, or other non-labor costs'), which implicitly distinguishes it from labor-related tools like autotask_create_time_entry. However, it doesn't explicitly mention when NOT to use it or name specific alternatives among siblings.

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