autotask_create_ticket

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

No annotations are provided, so the description carries full burden. The description does not disclose any behavioral traits such as side effects (e.g., triggering notifications, validation rules, required permissions), success/failure outcomes, or default values. For a mutation tool, this is insufficient.

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 (4 words), which is concise but lacks essential context. It is not poorly structured, but it could be expanded to include critical details without being verbose.

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 21 parameters and no output schema, the description should provide more context about required fields, interdependencies (e.g., issueType/subIssueType, assignedResourceID/assignedResourceRoleID), and typical usage patterns. Currently, it offers almost no guidance for correct usage.

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 adds no extra meaning beyond the schema. Baseline 3 is appropriate given the coverage.

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' clearly states the action and resource, but it does not differentiate this tool from other creation tools in the sibling list (e.g., autotask_create_task, autotask_create_project). The verb 'Create' and resource 'ticket record' are specific, but lack contextual distinction.

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., when to create a ticket via this tool vs. using autotask_create_ticket_note, etc.). There is no mention of prerequisites, required parent objects, or typical use cases.

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