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 of behavioral disclosure. It mentions retrieving 'detailed information' and 'full ticket data,' but doesn't cover critical aspects like whether this is a read-only operation (implied by 'Get'), error handling, rate limits, or authentication requirements. For a tool with zero annotation coverage, 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 concise with two clear sentences: one stating the purpose and another providing usage guidance. It's front-loaded with the core function and avoids unnecessary details. However, the second sentence could be slightly more specific to enhance clarity without losing efficiency.

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 tool's moderate complexity (2 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and hints at usage, but lacks details on behavioral traits, error cases, or output format. Without annotations or output schema, more context would be beneficial for safe and effective use.

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 the schema already documents both parameters ('ticketID' and 'fullDetails') thoroughly. The description adds minimal value by implying 'full ticket data' relates to the 'fullDetails' parameter, but doesn't provide additional context beyond what's in the schema. This meets the baseline for high schema 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 clearly states the tool's purpose: 'Get detailed information for a specific ticket by ID.' It specifies the verb ('Get'), resource ('ticket'), and identifier ('by ID'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'autotask_search_tickets' or 'autotask_get_ticket_attachment', which would be needed for a perfect score.

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 some guidance with 'Use this for full ticket data when needed,' which implies this tool is for detailed retrieval rather than searching or listing. However, it doesn't explicitly state when to use alternatives (e.g., 'autotask_search_tickets' for filtering multiple tickets) or mention prerequisites like authentication, leaving room for improvement.

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