autotask_create_ticket

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

No annotations exist, so the description bears full responsibility for behavioral disclosure. It only states 'Create new ticket record' with no details on side effects (e.g., permanent creation), authorization requirements, rate limits, or whether it overwrites existing data. This is insufficient 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?

The description is very short (one phrase), but lacks structure and essential information. While concise in word count, it sacrifices clarity and completeness. For a tool with 21 parameters, a more structured description (e.g., listing required fields or behavioral notes) would be warranted.

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 the tool's complexity (21 parameters, 3 required, no output schema), the description is severely incomplete. It does not mention required fields, return values, error behavior, or prerequisites. For an agent to correctly invoke this tool, far more context 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?

Schema description coverage is high (81%), so the schema already documents most parameters. The description does not add any parameter meaning beyond what the schema provides. Baseline of 3 is appropriate since the description does not contradict or redundantly explain parameters.

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 new ticket record' states the action and resource clearly, but is too generic. It does not differentiate from sibling tools like autotask_update_ticket or autotask_search_tickets, though the name alone does hint at creation. The description adds minimal value beyond the name.

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. There are many sibling tools for tickets (search, update, delete, etc.), but the description offers no context for selection. The schema references other tools (e.g., autotask_get_field_info) but the description itself lacks any usage guidelines.

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