autotask_get_ticket_details

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

No annotations are provided, so the description must convey behavioral traits. It indicates a read operation and lists return contents, but does not mention side effects, authentication requirements, or any constraints.

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, efficient sentence with front-loaded verb and resource. No wasted words, but could be slightly improved by clarifying the role of fullDetails or differentiating from search.

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 absence of an output schema, the description partially compensates by listing included data elements. However, it does not fully describe the return structure or expected fields, which may be insufficient for agents needing precise details.

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%, so both parameters are already described. The description adds minimal extra value beyond the schema for ticketID and fullDetails. The phrase 'including notes, time entries, and custom fields' hints at what fullDetails=true provides, but the schema already explains this.

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 purpose: retrieving full ticket details, and specifies included components (notes, time entries, custom fields). This distinguishes it from sibling tools like autotask_search_tickets (which returns summaries) and autotask_get_ticket_note (which is more specific).

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 does not explicitly state when to use this tool vs alternatives. It implies retrieval of a single ticket with full details, but lacks guidance on when to use this over search_tickets (for listing) or other get tools.

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