autotask_create_ticket_charge

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

No annotations exist, so the description must fully disclose behavior. It only says 'Create charge' implying mutation, but lacks details on error conditions (e.g., missing ticket), reversibility, permissions, rate limits, or effects on other entities. This is insufficient for a mutation tool with 12 parameters.

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?

A single sentence of 8 words, extremely concise with no repetition or filler. Every word serves the purpose of stating the tool's function.

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 12 parameters, no output schema, and no annotations, the description is too minimal. It does not explain return values, error handling, prerequisites, or side effects. A creation tool of this complexity requires more guidance for correct 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 coverage is 100% with all parameters described clearly (e.g., chargeType references autotask_get_field_info). The description adds no extra meaning beyond the schema, meeting the baseline score.

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 'Create charge on ticket for materials, costs, or expenses' clearly states the action (create charge) and resource (ticket), and provides examples. It implicitly distinguishes from sibling tools like autotask_create_expense_item (for expense reports) or autotask_create_time_entry (for labor), but does not explicitly differentiate.

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 guidance is provided on when to use this tool versus alternatives (e.g., autotask_create_expense_item, autotask_create_time_entry). There is no mention of prerequisites, context, or exclusion criteria, leaving the agent to guess when this charge creation is appropriate.

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