get_ticket_list_items

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

No annotations are provided, so the description carries the full burden. It explicitly states 'Read-only' and mentions pagination, which are positive behavioral disclosures. However, it does not describe return format, error handling, rate limits, or auth requirements. This is a modest level of transparency for a read operation with no annotations.

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?

Two sentences with minimal waste. The core action and key parameters are front-loaded, and the origin of IDs is clearly stated in the second sentence. Every word 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 no output schema, the description covers the essential inputs and their provenance. It states pagination and read-only nature. It could elaborate on response format or pagination details, but the tool's simplicity and the provision of ID sources make it sufficiently complete for an agent to invoke it 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?

With 0% schema description coverage, the description compensates well by explaining the purpose of all parameters: `list_id` (source: list_ticket_lists), `user_ns` (filter, source: find_contact), `title` (filter), and `page` (implicitly via 'paginated'). It adds meaning beyond field names, though it does not specify exact matching semantics or value formats.

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 ('List') and resource ('items in one ticket list'), and clarifies it is paginated. It also indicates filter options and provides provenance for key IDs, distinguishing it from sibling tools like list_ticket_lists (which lists lists) and get_order (which retrieves a single order). This is a clear, unambiguous purpose.

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 implies usage by stating that `list_id` comes from `list_ticket_lists` and `user_ns` comes from `find_contact`, giving context on how to obtain parameters. However, it does not explicitly state when to use this tool vs. alternatives or provide exclusions. The guidance is adequate but not explicit about alternative selection.

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