autotask_search_ticket_checklist_items

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

The description indicates the tool lists all checklist items with completion status, implying a read operation. No annotations are provided, so the description carries the full burden. It does not disclose any potential side effects, pagination, or filtering behavior, but for a simple list tool, this is minimally adequate.

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 consists of two concise sentences. The first states the purpose and output, and the second adds a critical constraint. Every sentence is necessary and efficient with no wasted words.

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?

For a simple tool with one required parameter and no output schema, the description covers the essential purpose and a key constraint. It could be improved by briefly describing the output format, but it is nearly complete for its simplicity.

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%, as the only parameter (ticketId) is already described in the schema. The tool description adds the context that it is a sub-resource constraint, but does not add significant new meaning beyond the schema's definition.

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 uses the verb 'List' and specifies the resource 'checklist items on a ticket', including their completion status. It clearly differentiates from sibling tools like autotask_search_tickets by stating checklist items are a sub-resource of a ticket.

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 explicitly states that a ticket ID is required and that checklist items cannot be queried without it. It provides clear context for when to use the tool, but does not mention when not to use it or suggest alternatives.

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