autotask_search_service_call_tickets

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

The description discloses that it is a search operation, which implies no side effects. However, no annotations are provided, so the description carries the full burden. It does not mention pagination behavior for pageSize (default, max), or whether both filters can be used together. Schema already covers parameter details.

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 clearly state the tool's purpose and usage. No redundant or extraneous information.

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 is complete for a search tool with a simple input schema and no output schema. It explains the use case and the two primary filters. However, adding a note about pagination or default pageSize would improve completeness. Given the low complexity, this is sufficient.

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 each parameter's meaning is already clear from the schema. The description adds context by explaining the overall purpose, which helps agents understand how to use the filters in combination. However, the description does not add new parameter-specific details beyond the 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 it searches for ticket associations on service calls, and provides two specific use cases: finding tickets linked to a service call or finding service calls containing a specific ticket. This distinguishes it from sibling tools that search for tickets alone (autotask_search_tickets) or service calls alone (autotask_search_service_calls).

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 mentions when to use this tool ('use this to find which tickets are linked to a service call, or which service calls contain a specific ticket'), providing clear context. However, it does not explicitly state when not to use it or mention alternatives like autotask_search_tickets for plain ticket searches.

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