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 bears full burden. It merely says 'search for ticket associations' without explaining behavior such as whether both filters can be combined (AND vs OR), default pagination, or the format of results. The agent cannot infer what the response looks like or how results are returned.

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?

Two sentences that front-load the action and purpose, with no wasted words. Efficient and easy to parse.

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 description covers purpose and parameter roles but lacks information about output format or pagination behavior. Since no output schema exists, the description should at least hint at the structure of results, which it does not.

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 description does not add significant meaning beyond the schema; it only frames them as filters for associations. Baseline 3 applies.

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 it searches for ticket associations on service calls, specifying bidirectional lookup: which tickets are linked to a service call or which service calls contain a ticket. This distinct purpose is well differentiated from sibling search tools like autotask_search_service_calls and autotask_search_tickets.

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 tells when to use this tool: to find links between tickets and service calls. It implies the bidirectional nature but does not explicitly exclude cases where other tools (e.g., search_tickets or search_service_calls) are more appropriate.

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