autotask_get_ticket_details

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

No annotations provided. Description only says it retrieves full details but does not disclose behavior like authentication needs, rate limits, error handling for invalid ticket IDs, or performance implications of the fullDetails flag.

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?

Single sentence with no unnecessary words. Every part earns its place.

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?

No output schema exists, yet the description does not specify the structure of the returned ticket details, leaving an AI agent uncertain about the response format. For a retrieval endpoint, more detail on output would be helpful.

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 the schema already explains both parameters. The description adds no additional semantic value beyond the parameter descriptions.

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?

Description clearly states the action ('Get'), the resource ('full ticket details'), and explicitly lists included sub-items (notes, time entries, custom fields). This distinguishes it from sibling tools like autotask_get_ticket_note or autotask_search_tickets.

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 on when to use this tool versus alternatives such as search_tickets (for summaries) or get_ticket_note (for specific notes). Also no mention of the trade-off for the fullDetails parameter.

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