autotask_search_tickets

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

No annotations are provided, so the description must disclose behaviors. It mentions a pagination limit (Max 500/page) but does not explicitly state that this is a read-only operation or describe return format. The absence of destructive hints is acceptable 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 short (two sentences) and front-loaded with key filters. However, the inaccuracy regarding filters reduces its effectiveness. Brevity without correctness is not sufficient.

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 11 parameters, no output schema, and many sibling tools, the description is incomplete. It does not explain pagination defaults, return fields, or sorting. The misleading filters further harm completeness.

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?

The description mentions 'queue' and 'priority' as filters, but these are not present in the input schema. This contradicts the actual parameters and misleads the agent. Schema coverage is high, but the description adds confusion rather than clarity.

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 function: search tickets by company, queue, status, priority. It also distinguishes from autotask_get_ticket_details for full data, and from many create/update siblings, making purpose specific.

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?

It explicitly recommends using autotask_get_ticket_details for full data, providing an alternative. However, it does not specify when not to use this tool versus other search tools, and the mention of 'queue' and 'priority' is misleading as those filters are not in the schema.

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