autotask_create_ticket_charge

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

No annotations provided, so description carries full burden. It only states 'Create charge on ticket' without disclosing side effects, permissions, error conditions, or idempotency. Minimal transparency beyond the implied creation action.

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 concise sentence that captures the core purpose without unnecessary words. It is front-loaded and efficient, though it could include a bit more structure (e.g., separate usage hints).

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?

With 12 parameters and no output schema, the description is minimal. The schema fills in parameter details, but the tool lacks information about return values or confirmation. For a creation tool, this is adequate but could be enhanced.

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% with detailed parameter descriptions. The description adds no extra context beyond the schema. Per guidelines, baseline is 3 when schema coverage is high, and no additional value provided.

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?

Description clearly states 'Create charge on ticket for materials, costs, or expenses.' It uses a specific verb ('Create') and resource ('charge on ticket'), distinguishing it from sibling tools like autotask_create_ticket or autotask_create_ticket_note.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for adding charges but does not mention exclusions or alternative methods. Context from sibling names provides some implicit differentiation.

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