autotask_search_service_call_tickets

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 correctly implies a read-only search operation, but lacks detail on response format, pagination behavior, or potential limitations. While the basic behavior is clear, more transparency would be beneficial for a search tool.

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, consisting of two sentences that front-load the core purpose. Every sentence is functional and adds necessary context without redundancy.

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?

The tool has 3 optional parameters and no output schema. While the description explains the search intent, it does not clarify what the response contains (e.g., a list of associations, full objects, or just IDs). For a search tool, providing an overview of the return format 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?

Schema description coverage is 100%, so the baseline is 3. The description adds value by explaining the relationship between the two filters: 'ticketId' retrieves service calls containing that ticket, and 'serviceCallId' retrieves tickets linked to that call. This contextual meaning is not present in the schema alone.

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: searching for ticket associations on service calls. It explicitly mentions two distinct use cases: finding tickets linked to a service call or service calls containing a specific ticket. This separates it clearly from sibling tools like 'autotask_get_service_call' or 'autotask_create_service_call_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 provides explicit usage guidance: 'Use this to find which tickets are linked to a service call, or which service calls contain a specific ticket.' It does not explicitly mention when not to use it or list alternatives, but the guidance is clear and actionable given the sibling tools.

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