get_tickets_contact

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds valuable context: results are in reverse chronological order, have no search ranking or filtering, and are formally assigned. It does not cover permissions, errors, or pagination details, but the provided traits are useful.

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 three sentences long and front-loads the core purpose. There is minor redundancy between the first and second sentences ('Get' and 'retrieves tickets') but overall it is tight and earns its place.

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 list tool with an output schema, the description adequately covers purpose, usage context, and return ordering. It lacks explicit mention of pagination behavior, but the schema documents page and per_page parameters, so the gap is acceptable.

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 schema covers 100% of parameters with descriptions, so the baseline is 3. The description reinforces that multiple contact IDs can be used but does not add substantial meaning beyond the schema, such as formatting or constraints for page/per_page.

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 uses a specific verb ('Get') and resource ('tickets assigned to one or more contacts'), clearly indicating the tool's scope. This distinguishes it from sibling tools like get_tickets_company and get_tickets_by_queue, which target different filters.

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 states 'Use this after finding contacts with search_contacts', giving clear contextual guidance on when to invoke the tool. It does not mention exclusions or directly compare to alternatives, so it stops short of a 5.

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