List an organization's tickets

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

Annotations (readOnlyHint=true, openWorldHint=true) cover safety and completeness. Description adds ordering detail and id source, but doesn't mention pagination, result structure, or limit behavior beyond schema.

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. Core function stated first, followed by practical guidance on obtaining the required parameter.

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?

No output schema, so description should clarify return format (e.g., list of ticket objects) and pagination. Current description leaves these unspecified, though openWorldHint implies incomplete results.

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 already covers parameters well (100% coverage), but description adds value by explaining ordering ('most recent first') and how to derive organizationId from other records, which aids correct usage.

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 verb 'List', resource 'tickets belonging to an organization', and sorting 'most recent first'. It distinguishes from sibling tools like zendesk_requester_tickets and zendesk_fetch_view_tickets by the grouping criterion.

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?

Provides source for organization id but offers no guidance on when to use this tool versus alternatives like zendesk_search or zendesk_requester_tickets. Agent must infer usage from name alone.

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