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 the full burden of behavioral transparency. It implies a read-only search operation but does not disclose details such as pagination behavior, sorting, or rate limits. The description is adequate but lacks explicit reassurance of non-destructiveness or other traits.

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 two sentences long with no verbose or redundant phrasing. It front-loads the purpose and use cases efficiently, making it easy for the agent to quickly understand the tool.

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?

For a search tool with no output schema and no annotations, the description adequately explains the tool's functionality and input options. It could mention pagination (via pageSize) or result format, but the existing information is sufficient for an agent to use the tool correctly.

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%, meaning all parameters have descriptions in the schema. The description adds no additional meaning beyond what the schema provides, so it meets the baseline without enhancement.

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 specifies two use cases (finding tickets linked to a service call or finding service calls containing a specific ticket), distinguishing it from sibling tools like autotask_search_service_calls and autotask_search_tickets which do not show 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 context on when to use the tool (to find links between tickets and service calls). It does not explicitly mention when not to use it or list alternatives, but the use cases are specific enough to guide the agent without exclusion.

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