autotask_create_ticket

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

No annotations are provided, so the description carries the full burden of behavioral transparency. The description only states 'Create a new ticket in Autotask', which implies a write operation but does not disclose any behavioral traits like required permissions (e.g., authentication), side effects (e.g., triggers notifications), rate limits, or response behavior. However, the schema provides some constraints (e.g., assignedResourceID requires assignedResourceRoleID) which partially compensates. The description is adequate but lacks detail.

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 concise (one short sentence). It is front-loaded and to the point. While brevity is good, the sentence is so short that it sacrifices detail. However, given the extensive schema, the description wisely leaves details to the schema, making it efficient.

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?

The tool has 21 parameters, many complex (picklists, required relationships). No output schema exists, so the description should hint at what the tool returns (e.g., ticket ID). The description lacks this. However, the rich schema with cross-references to other tools (e.g., autotask_get_field_info) provides good context for selecting valid parameter values. The description itself is incomplete, but the schema compensates somewhat.

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 baseline is 3. The description adds minimal meaning beyond what the schema provides, but the schema itself is well-documented with examples and references to auxiliary tools (e.g., 'Use autotask_list_queues to discover valid IDs'). The description does not add new semantic understanding beyond the parameter descriptions already present.

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 ('Create'), the resource ('a new ticket'), and the system ('Autotask'). It distinguishes this from sibling tools like autotask_create_ticket_note, autotask_create_ticket_attachment, etc., which create related but different resources. However, it does not explicitly contrast with these siblings, and the title is null, so it relies solely on the description.

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 no guidance on when to use this tool versus alternatives (e.g., when to use autotask_update_ticket instead, or prerequisites like companyID must exist). The input schema includes some helpful hints (e.g., use autotask_list_queues, autotask_get_field_info), but these are not part of the description itself. The description is too brief to offer usage context.

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