autotask_search_ticket_checklist_items

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 indicates this is a read-only listing operation and does not modify anything. It adds the sub-resource constraint beyond the schema but does not disclose details like pagination, results limit, or output format (e.g., only completion status fields).

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 two sentences long, front-loaded with the primary purpose, and efficiently conveys the key constraint about the ticket ID dependency. It is concise and well-structured.

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 has only one parameter with full schema coverage and no output schema, the description sufficiently covers the purpose and key constraint. For a simple listing operation, the description is complete and leaves no major gaps.

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, already documenting the ticketId parameter. The description adds context that the ticketId is required and provides the relationship (sub-resource), but does not add new semantics beyond what the schema provides.

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 lists all checklist items on a ticket with their completion status. It specifically identifies the resource (checklist items) and the action (list), and distinguishes from sibling tools like autotask_create_ticket_checklist_item and autotask_delete_ticket_checklist_item.

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 checklist items are a sub-resource of a ticket and cannot be queried without a ticket ID, which clarifies the prerequisite. However, it does not provide guidance on when to use this tool versus other search tools for tickets or checklist items, though the uniqueness of the operation makes it less necessary.

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