Search Re:lation tickets

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

No annotations provided, so description carries full burden. Only mentions 'returns a paginated list'. Does not disclose sorting, rate limits, performance, error handling, or what happens with no results. Authentication needs are implicit but not stated.

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?

Single sentence is concise but under-informative. Could be improved by adding structure or more details without being verbose. Currently only slightly above tautology.

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 9 parameters, no output schema, and no annotations, the description is incomplete. Lacks details on return format, pagination specifics, and guidance on filter combinations. Does not differentiate from get_ticket or other search tools.

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 low (22%). Description only lists filter categories but does not explain individual parameters like message_box_id, assignee_ids, label_ids, etc. Does not add value beyond the sparse schema descriptions for status_cds and search_query.

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?

Description clearly states the verb 'Search' and resource 'tickets', lists filter criteria (status, label, assignee, date range, free-text query), and mentions pagination. Distinguishes from sibling tools like get_ticket (single ticket) and search_customers.

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?

No guidance on when to use this tool vs alternatives. Does not mention when not to use, prerequisites, or context like needing a message_box_id. Sibling tools exist but description lacks any comparative advice.

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