autotask_get_ticket_details

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

No annotations are provided, so the description carries the full burden. It states 'get detailed information' but does not disclose any behavioral traits such as read-only nature, what happens if the ticket ID is invalid, or any rate limits. The description is minimal and lacks transparency about the tool's behavior beyond its basic function.

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 only two sentences long, directly stating the purpose and a usage hint. It is front-loaded with the action and resource, making it easy to scan quickly. No unnecessary words or details.

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 that there is no output schema and no annotations, the description is somewhat complete: it explains what the tool does and when to use it. However, it lacks information about the return format, error handling, or any side effects. For a tool with only two parameters and no output schema, additional context would improve completeness.

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?

The input schema has 100% description coverage for both parameters (ticketID and fullDetails), so the schema already provides clear meaning. The description does not add any additional semantic information beyond what is in the schema. Baseline score of 3 is appropriate.

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 verb 'Get' and the resource 'detailed information for a specific ticket by ID'. Among many ticket-related siblings, this is distinct from get_ticket_attachment, get_ticket_note, etc., and the description specifies 'ticket details', which differentiates it.

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 says 'Use this for full ticket data when needed', which provides some guidance on when to use it. However, it does not mention when not to use it or suggest alternatives like autotask_search_tickets for partial data. The guidance is present but incomplete.

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