List Zendesk Tickets

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

Annotations already declare the tool as readOnly, idempotent, non-destructive, and openWorld. The description adds behavioral context about cursor-based pagination and sorting, which is useful beyond annotations but does not cover every aspect (e.g., no mention of rate limits).

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, no wasted words, front-loaded with the most important information. Highly concise while conveying all necessary details.

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 the simple schema with two parameters, comprehensive annotations, and no output schema, the description fully covers the tool's behavior and usage, leaving no gaps for an agent to misinterpret.

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 has 100% coverage for both parameters. The description adds significance by contrasting page_size with per_page from search_tickets, providing additional meaning beyond the schema descriptions.

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 verb (list), resource (tickets), and key features (cursor-based pagination, sorted by most recently updated). It distinguishes itself from the sibling search_tickets which uses offset-based pagination.

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?

Explicitly explains that page_size should be used instead of per_page (used by search_tickets), and that pagination is done by passing the returned cursor. Provides clear when-to-use guidance and differentiates from an alternative.

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