autotask_search_service_call_tickets

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

With no annotations provided, the description carries full burden for behavioral disclosure. The description only states the search action but omits important traits: it does not confirm read-only behavior (though implied), does not mention pagination behavior despite the pageSize parameter, and does not describe what the response contains (e.g., list of association objects with key fields). This lack of detail leaves the agent guessing about side effects and output structure.

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 extremely concise: two short sentences with no extraneous words. The first sentence states the action and resource, the second provides usage guidance. It is front-loaded and every sentence serves a purpose. This is a model of efficient tool descriptions.

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 (3 parameters, no output schema, no annotations), the description is insufficiently complete. It lacks details about the return format (expected fields or structure), the effect of not providing any filter (potential full list?), and any prerequisites (e.g., valid ticket or service call IDs). A complete description would at least mention the output is a list of ticket-service call association objects.

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 all three parameters (pageSize, ticketId, serviceCallId) with descriptions. The tool's description text does not add any additional meaning beyond restating the filter capabilities. Per guidelines, baseline is 3 when schema coverage is high and description offers no extra value. The description could hint at combining filters or default page size, but it doesn't.

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 uses a specific verb ('Search') and resource ('ticket associations on service calls'). It also explicitly differentiates two use cases (finding tickets linked to a service call, and finding service calls containing a ticket), which helps distinguish it from sibling tools like autotask_search_tickets or autotask_get_ticket_details.

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 use cases ('find which tickets are linked to a service call, or which service calls contain a specific ticket'), giving clear context for when to use the tool. However, it does not mention when not to use it or suggest alternative tools, though the sibling list contains many search tools that could overlap (e.g., autotask_search_service_calls). A brief note on exclusion would improve it.

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