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 must carry the full burden. It only states the purpose and use cases but does not disclose behavioral details such as pagination behavior (pageSize default/max are in schema but not described), sorting, or the effect of providing both serviceCallId and ticketId (AND vs OR). This lack of transparency is significant 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 with just two clear sentences. Every word adds value, and it is front-loaded with the core purpose. No unnecessary verbiage.

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?

No output schema is provided, so the description should explain the return format or structure of results. It does not mention what the search returns (e.g., list of associations with service call and ticket IDs). Additionally, the parameter descriptions in the schema are minimal, and the description does not compensate for the lack of output schema details.

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 coverage is 100% with descriptions for all three parameters. The tool description adds no additional meaning beyond what is already in the schema. For instance, it does not clarify the logical relationship when both serviceCallId and ticketId are provided (e.g., AND or OR). Baseline 3 is appropriate given the rich schema.

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: 'Search for ticket associations on service calls.' It specifies the two use cases: finding tickets linked to a service call or service calls containing a specific ticket. This distinguishes it from sibling search tools like autotask_search_service_calls and autotask_search_tickets by focusing specifically on associations.

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 clear when-to-use scenarios: finding links between tickets and service calls. However, it does not explicitly mention when not to use the tool (e.g., for creating or deleting associations) or name alternative tools like autotask_create_service_call_ticket. The implied read-only nature is present but not explicitly stated.

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